Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Http looping on 416
23-11-2016, 03:47 PM
Post: #6
RE: Http looping on 416
(23-11-2016 03:28 PM)simonc Wrote:  I don't think that's a valid response. Shouldn't a HTTP 1.1 server supply either a Content-Length header or set Transfer-Encoding: chunked? It looks like your server's response is using the old HTTP 1.0 approach of just closing the connection to indicate end of stream; this isn't valid in HTTP 1.1.

I think it is valid for an HTTP 1.1 server to do this for a response. (It would not be allowed for a request.) See this section, specifically:

5.By the server closing the connection. (Closing the connection cannot be used to indicate the end of a request body, since that would leave no possibility for the server to send back a response.)
Find all posts by this user


Messages In This Thread
Http looping on 416 - medoc92 - 23-11-2016, 07:47 AM
RE: Http looping on 416 - simonc - 23-11-2016, 01:52 PM
RE: Http looping on 416 - medoc92 - 23-11-2016, 03:14 PM
RE: Http looping on 416 - simonc - 23-11-2016, 03:28 PM
RE: Http looping on 416 - simoncn - 23-11-2016 03:47 PM
RE: Http looping on 416 - simonc - 23-11-2016, 03:52 PM
RE: Http looping on 416 - medoc92 - 23-11-2016, 04:13 PM
RE: Http looping on 416 - simonc - 23-11-2016, 03:30 PM
RE: Http looping on 416 - medoc92 - 24-11-2016, 05:31 PM
RE: Http looping on 416 - simoncn - 24-11-2016, 06:21 PM

Forum Jump: