HTTP 308 Incompetence Expected
insanecoding.blogspot.com
HTTP 308 Incompetence Expected
1–10 of 44 posts
Re: HTTP 308 Incompetence Expected
#2Side note: don’t use serif fonts such as Georgia with small characters. I changed the font to Helvetica and the readability was much better.
Re: HTTP 308 Incompetence Expected
#3Side note: don’t use serif fonts such as Georgia with small characters. I changed the font to Helvetica and the readability was much better.
Both the font size and colour scheme on that page hurt my eyes.
Re: HTTP 308 Incompetence Expected
#4Side note: don’t use serif fonts such as Georgia with small characters. I changed the font to Helvetica and the readability was much better.
Tell the author. This is an aggregator.
Re: HTTP 308 Incompetence Expected
#5Re: HTTP 308 Incompetence Expected
#6Can anyone here provide any explanation of how the changes in HTTP2 might not be idiotic?
The changes discussed in the post just seem dumb to me, but I assume there has to be some reasoning behind them.
Re: HTTP 308 Incompetence Expected
#7I think the author of this blogpost has a few things off:
- HTTP2 != httpbis. Both work is being done by the same working group "httpbis". http://datatracker.ietf.org/wg/httpbis/charter/ covers this. httpbis (http://stackoverflow.com/questions/9105639/httpbis-what-does...) was originally chartered to revise HTTP/1.1 (RFC2616) The working group will refine RFC2616 to: * Incorporate errata and updates (e.g., references, IANA registries, ABNF) * Fix editorial problems which have led to misunderstandings of the specification * Clarify conformance requirements * Remove known ambiguities where they affect interoperability * Clarify existing methods of extensibility * Remove or deprecate those features that are not widely implemented and also unduly affect interoperability * Where necessary, add implementation advice * Document the security properties of HTTP and its associated mechanisms (e.g., Basic and Digest authentication, cookies, TLS) for common applications
As for the HTTP/2 work, here's a snippet from the charter on that: The Working Group will produce a specification of a new expression of HTTP's current semantics in ordered, bi-directional streams. As with HTTP/1.x, the primary target transport is TCP, but it should be possible to use other transports.
- He seems to think the httpbis folks gratuitously redefined 301. It should be noted that RFC2616 (which, by definition, predates the httpbis work since httpbis is defined to revise RFC2616) had already noted the issue with 301 (http://tools.ietf.org/html/rfc2616#section-10.3.2): Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.
- It's unclear to me whether or not the author acknowledges the existence of buggy implementations as noted in section 10.3.2. It's an open question as to what to do in the presence of buggy implementations. From a server standpoint, if the client is buggy, and you don't want to break the client (willingness to break clients probably depends on how many of the server's users use that client), then you will attempt to work around it, irrespective of what the standard says. Therefore, it's simply pragmatic to ignore the spec if it doesn't mirror reality, and pragmatic spec editors may update the spec to acknowledge this difference.
- As far as current status of the various 308 usages, Julian (author of the 308 draft) is lobbying major user agents to adopt this, and has written up a status update on the Chromium bug tracker: https://code.google.com/p/chromium/issues/detail?id=109012#c....
Re: HTTP 308 Incompetence Expected
#8Side note: don’t use serif fonts such as Georgia with small characters. I changed the font to Helvetica and the readability was much better.
Both the font size and colour scheme on that page hurt my eyes.
Just add this custom css to the page and it should be much more legible:
body { background: white; color: black; line-height: 27px; }
#outer-wrapper { font-family: 'Lucida Grande'; font-size: 11pt; }
Re: HTTP 308 Incompetence Expected
#9Can anyone here provide any explanation of how the changes in HTTP2 might not be idiotic? The changes discussed in the post just seem dumb to me, but I assume there has to be some reasoning behind them.
I think the reasoning is "Embrace, Extend, Extinguish"
Re: HTTP 308 Incompetence Expected
#10Side note: don’t use serif fonts such as Georgia with small characters. I changed the font to Helvetica and the readability was much better.
Tell the author. This is an aggregator.
The OP might be the author and thus will see this comment. In any case, it can be useful for other people.