I know this is old, but here is my understanding of “100 Continue” Your server is supposed to validate the request based on header alone from the client i.e. if the request is invalid, don’t send “100 Continue” but actual http error instead e.g. 403. This should prevent the client from posting the data which … Read more
Solutions barely exist for this, and the documentation is poor at best for supporting both on one server. The trick here is to understand that client proxy configurations may send https requests to an http proxy server. This is true for Firefox if you specify an HTTP proxy and then check “same for all protocols”. … Read more
A Keep Alive HTTP header since HTTP 1.0, which is used to indicate a HTTP client would like to maintain a persistent connection with HTTP server. The main objects is to eliminate the needs for opening TCP connection for each HTTP request. However, while there is a persistent connection open, the protocol for communication between … Read more
Not including the accept-encoding header implies that you may want the default encoding, i.e. identity. The caveat here is that the RFC2616 sec 14.3 allows the server to assume any available encoding is acceptable. To explicitly request plain text, set ‘accept-encoding: identity’
Does the HTTP 200 code also work as an acknowledgment that document has been received? No. Not at all. It is not even a guarantee that the document was completely transmitted. The response code is in the first line of the response stream. The server could fail, or be disconnected from the client anywhere between … Read more
how exactly does http.sys work [closed]
I use the same scenario as you and use PUT for it. You have to ask yourself: “when I send the same request twice, does this make a different state on server?” If yes, use POST, if no use PUT.
Typically, you’d send a 401 if the client can authenticate and solve the problem, but since you don’t provide a way to authenticate in the API, I’d suggest returning a 403 error (forbidden) instead. This won’t require the header and will indicate to the client that it is unable to access the service.
Cookie names are case-sensitive. The RFC does not state that explicitly, but each case-insensitive comparison is stated so explicitly, and there is no such explicit statement regarding the name of the cookie. Chrome and Firefox both treat cookies as case-sensitive and preserve all case variants as distinct cookies. Test case (PHP): print_r($_COOKIE); setcookie(‘foo’, ‘123’); setcookie(‘Foo’, … Read more
You can serve any content over HTTP such as HTML, images, sound, video, etc. SOAP is an XML-based encoding of messages that are typically sent over HTTP, but could be sent over SMTP or even FTP, although I’ve never seen such a system used in a production environment. Just like HTTP sits on top of … Read more