TL; DR: Chrome interprets this response header as keep-alive and maintain a peristent connection while Firefox closes each connection. I stumbled over this question as I tried to optimize the page loading time for my website. In the referenced RFC I didn’t find anything about how multiple entries in the Connection header may be properly … Read more
The content type is per specification multipart/form-data. This is a special content type which can be visualized as multiple sub-requests in one big request. Each of those sub-requests (one form-data element) has their own set of headers. The content type of the actual data is in there. Here’s an example how it look like with … Read more
There is no “full specification” — it’s a de facto standard. The X- in front of a header name customarily* has denoted it as experimental/non-standard/vendor-specific. Once it’s a standard part of HTTP, it’ll lose the prefix. There’s some work from the IETF on standardizing it, but it’s just at the draft stages, as far as … Read more
The syntax of a boundary is: boundary := 0*69<bchars> bcharsnospace bchars := bcharsnospace / ” ” bcharsnospace := DIGIT / ALPHA / “‘” / “(” / “)” / “+” / “_” / “,” / “-” / “.” / “/” / “:” / “=” / “?” And the body of a multipart entity has the syntax … Read more
In case the other answers weren’t clear enough: First you gzip the body with zlib (this can be done in a stream so you don’t need the whole thing in memory at once, which is the whole point of chunking). Then you send that compressed body in chunks (presumably the ones provided by the gzip … Read more
HTTP is a stateless protocol, in other word the server will forget everything related to client/browser state. Although web applications have made it virtually look like stateful. A stateless protocol can be forced to behave as if it were stateful. This can be accomplished if the server sends the state to the client, and if … Read more
HTTP/1.1 without pipelining: Each HTTP request over the TCP connection must be responded to before the next request can be made. HTTP/1.1 with pipelining: Each HTTP request over the TCP connection may be made immediately without waiting for the previous request’s response to return. The responses will come back in the same order. HTTP/2 multiplexing: … Read more
Hyper Text Transfer Protocol (HTTP) is a protocol used for transferring web pages (like the one you’re reading right now). A protocol is really nothing but a standard way of doing things. If you were to meet the President of the United States, or the king of a country, there would be specific procedures that … Read more
To answer your questions: How to deal with unauthorized requests? The way you described it is pretty much the recommended way for a RESTful service. As far as I can see there is absolutely nothing wrong with that. What WWW-Authenticate header should 401 responses supply? In general the WWW-Authenticate header tells the client what kind … Read more
You need to look at the definition of the header field: http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.14.17 Content-Type = “Content-Type” “:” media-type so it takes a single media-type, which is defined by the grammar you quoted above. So the answer is: a single type/subtype, followed by optional parameters.