I’ve done some massive HTTP stuff lately which included a full re-read of some (all?) HTTP releated RFCs – some of them I first studied years ago. It’s not that simple as it was back those years, but it’s good to reconsider the standards.
Driven by some passion I’ve done peek and poke over diverse code-bases as well as on wordpress. Interestingly it turns out, even with a stable internet standard specification (at least somehow stable), most developers tend to not care about it (properly). I know there is a difference between getting something on the run to the run and to write a proper implementation. Every tool for it’s need. But if some of you are in the mood for some quality control I suggest to create / apply a HTTP compability testsuite on the wordpress application. My findings are somehow by accident and already revealed multiple points of interest.
Some HTTP/Header related Tickets lately:
- Ticket #13909 – HTTP redirect should return a hypertext fragment
- Ticket #13940 – get_status_header_desc() returns HTTP 1.1 status codes for HTTP 1.0
- Ticket #13955 – Updated / corrected List of HTTP status codes
- Ticket #14062 – some Location headers are using relative url’s
- Ticket #14069 – do_robots() ignores charset setting
- HTTP – Hypertext Transfer Protocol (W3C)
- Hypertext Transfer Protocol Bis (IETF httpbis Working Group)
- HTTP Status Codes in Use (18 Jun 2010 by hakre)