What happened to 430?
Asked Mark Nottingham on Twitter, 430 is used in this other draft RFC:
http://tools.ietf.org/html/draft-nottingham-http-pipeline-01
(It's 430 Would Block.)
New HTTP Codes
81–84 of 84 posts
Re: New HTTP Codes
#82I wish HTTP requests submitted time zone information.
It has been proposed several times. 2008: http://tools.ietf.org/html/draft-sharhalakis-httptz-05 1995 - shot down because (paraphrasing) "I don't need this so neither should you": http://www.hpl.hp.com/personal/ange/archives/archives-95/htt... The general consensus seems to be that since this can never be all things to all people, we can't ever implement it. To me it seems like this is crying out for a Worse is Bette…
I think we'll see this discussion come around again soon; maybe it'll stick this time.
Re: New HTTP Codes
#83Earlier quoted context omitted.
The "Main differences from HTTP" section says this: "SPDY is intended to be as compatible as possible with current web-based applications. This means that, from the perspective of the server business logic or application API, nothing has changed. To achieve this, all of the application request and response header semantics are preserved. SPDY introduces a "session" which resides between the HTTP application layer and…
> So from the point of view of e.g. GMail, it is making HTTP requests via XmlHttpRequest still is it not? No, it's making SDPY requests. It is, however, making that difference insignificant to the application developer using the xmlHttpRequest API. HTTP is a protocol not an API. This is exactly what the paper says; the protocol is designed to make the API differences very minimal. > And from the point of view of my D…
> No, Django doesn't talk HTTP -- Django talks WSGI or CGI. That hides many of the details of the protocol in use -- I imagine that you could run Django with a server that sends/receives web requests over FTP.
I don't know how you would make e.g that[1] work on FTP. Basically you would end up encapsulating HTTP inside FTP, not using one in place of the other.
A CGI script takes raw (yet conveniently split by the web server) HTTP data from ENV vars and stdin, and outputs HTTP data directly to stdout. Django HttpRequest and HttpResponse object merely provides a convenient helper for that and does not actually abstract anything. The web server pipes the response as is straight to the client via TCP (unless there is SSL, where it will just obliviously encrypt the stream).
To comply with that, as SPDY is a replacement to HTTP, mod_spdy transcodes stuff live [2].
[1] https://docs.djangoproject.com/en/dev/ref/request-response/#... [2] http://code.google.com/p/mod-spdy/wiki/Design
Re: New HTTP Codes
#84OMG really? Do we want to make HTTP even bigger? Don't we want to dump it for good and look for something more suitable to what the modern web needs instead?
What do you propose we do in he meantime, before all the existing servers and clients are migrated?
I propose HTTP 0.2, a subset of HTTP 1.1 with some simple extensions: http://http02.cat-v.org