get_status_header_desc() returns HTTP 1.1 status codes for HTTP 1.0

[hakre]

That does not work well together. I suggest adding a new parameter passing the http version to it so the return values can go conform.

Related: #9297

[hakre]

HTTP 1.0 Status Code and Reason Phrase

[hakre]

HTTP 1.1 Status Code and Reason Phrase

[dd32]

What set of HTTP 1.0 messages differ from those of the HTTP 1.1 set?

[markjaquith]

The reason phrase is for humans, and as such it can be anything we want it to be. We could serve 404 OH NO and it would be fine.

The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes are fully defined in section 10. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason- Phrase.

[hakre]

Replying to dd32:

What set of HTTP 1.0 messages differ from those of the HTTP 1.1 set?

I'm compiling a list, I stumbled over some constraints in #9297 that's why it takes a bit longer.

---

Replying to markjaquith:

The reason phrase is for humans, and as such it can be anything we want it to be. We could serve 404 OH NO and it would be fine.

Serving 426 OH NO for HTTP 1.0 would not be fine.

You must not return wrong status-codes (which would invalidate the full phrase) in HTTP 1.0 nor in HTTP 1.1.

Please do not needlessly hunt it down before this ticket can stand on it's own feet. I'm still on the issue. Same @nacion. Thanks.

[hakre]

New Headers in HTTP 1.1 compared to HTTP 1.0

• 100 : Continue
• 101 : Switching Protocols
• 203 : Non-Authoritative Information
• 205 : Reset Content
• 206 : Partial Content
• 300 : Multiple Choices
• 303 : See Other
• 305 : Use Proxy
• 307 : Temporary Redirect
• 402 : Payment Required
• 405 : Method Not Allowed
• 406 : Not Acceptable
• 407 : Proxy Authentication Required
• 408 : Request Time-out
• 409 : Conflict
• 410 : Gone
• 411 : Length Required
• 412 : Precondition Failed
• 413 : Request Entity Too Large
• 414 : Request-URI Too Large
• 415 : Unsupported Media Type
• 416 : Requested range not satisfiable
• 417 : Expectation Failed
• 504 : Gateway Time-out
• 505 : HTTP Version not supported

Changed Headers in HTTP 1.1 compared to HTTP 1.0

• 302 : Found
  • HTTP 1.0: 302 : Moved Temporarily
  • HTTP 1.1: 302 : Found

[hakre]

some small meat to feed the wild cats

[hakre]

There is no status code 306 in HTTP 1.1 or HTTP 1.0. Which version do you intend to support with WordPress?

[hakre]

WebDAV Status Code Extensions to HTTP/1.1

[hakre]

TLS Within HTTP/1.1

[hakre]

Transparent Content Negotiation in HTTP

[hakre]

An HTTP Extension Framework

[hakre]

Delta encoding in HTTP

[hakre]

Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)

[hakre]

In the end I must admit that I do not know wether or not that function should or should not return values without taking the HTTP version as well as the REQUEST METHOD into account. Next to the status code, that would be needed as context to properly find out. So thoughtfull comment by a core dev/contributer would be nice to know.

Regarding the other flaws I've found I'll create a new ticket.

[nacin]

Closed tickets don't have a milestone.

[hakre]

Related: #13955

[hakre]

I reopen it because the dicussion lately did fail to match the point this is about:

• How to deal with invalid Status Codes (not messages) on HTTP requests (e.g. using a non-existant status code in a HTTP/1.0 request)
• Which HTTP standard is to be supported by WordPress?

Please see this comment by me as well hakre.

[hakre]

Status Header Related: #3528

[rmccue]

To reiterate what Mark said, the reason doesn't matter, and RFC 2616 (HTTP 1.1) notes this (section 6.1.1:

The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.

[...]

The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, are presented below. The reason phrases listed here are only recommendations -- they MAY be replaced by local equivalents without affecting the protocol.

(Emphasis mine)

I won't close this, as I feel it's not my place to do so in this case.

[hakre]

To rephrase what I wrote in response to Mark, emphasis by me:

Replying to hakre:

Replying to markjaquith:
You must not return wrong status-codes (which would invalidate the full phrase) in HTTP 1.0 nor in HTTP 1.1.

As you can see I'm writing about codes, not phrases. This is the same for the title of this ticket.