Ticket #238 (closed design: fixed)
Requirements for user intervention during redirects
|Reported by:||firstname.lastname@example.org||Owned by:|
|Component:||p2-semantics||Severity:||Active WG Document|
The redirect status codes define requirements for user intervention; e.g.,
If the 301 status code is received in response to a request method that is known to be "safe", as defined in Section 7.1.1, then the request MAY be automatically redirected by the user agent without confirmation. Otherwise, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
However, this requirement is not often implemented by UAs.
In dealing with this issue, we need to consider the impact of #160.
Raised by Adam Barth at IETF78.
- Status changed from new to closed
- Resolution set to incorporated
- Milestone changed from unassigned to 19
- Status changed from closed to reopened
- Resolution incorporated deleted