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: ref for status code 308 #590

Merged
merged 2 commits into from Apr 18, 2018
Merged

bcp56bis: ref for status code 308 #590

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e45c8d7
bcp56bis: ref for308
reschke Apr 17, 2018
15ac8d8
fix ref syntax
reschke Apr 18, 2018
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 @@ -519,7 +519,7 @@ of an application's specification.

The 3xx series of status codes specified in {{!RFC7231}}, Section 6.4 are used to direct the user
agent to another resource to satisfy the request. The most common of these are 301, 302, 307 and
308, all of which use the Location response header field to indicate where the client should send
308 ({{?RFC7538}}), all of which use the Location response header field to indicate where the client should send
the request to.

There are two ways that this group of status codes differ:
Expand Down