Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bcp56bis: 302 *response* not *request* #591

Merged
merged 1 commit into from Apr 17, 2018
Merged

bcp56bis: 302 *response* not *request* #591

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-httpbis-bcp56bis.md
View file
Open in desktop
Expand Up @@ -544,7 +544,7 @@ code. However, they aren't required to do so; therefore, if an application using
redirects to be automatically followed, it needs to explicitly specify the circumstances when this
is required.

Applications using HTTP SHOULD specify that 301 and 302 requests change the request method from POST
Applications using HTTP SHOULD specify that 301 and 302 responses change the subsequent request method from POST
(but no other method) to GET, to be compatible with browsers.

Generally, when a redirected request is made, its header fields are copied from the original
Expand Down