Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem when action request doesn't have Content-Length header
04-07-2013, 08:12 AM (This post was last modified: 04-07-2013 08:13 AM by simonc.)
Post: #10
RE: Problem when action request doesn't have Content-Length header
(02-07-2013 06:11 PM)simoncn Wrote:  I've done some more research into this, and it seems your original impression is correct. See this page for the HTTP rules.

Thanks for doing this. I agree that it isn't valid for a HTTP/1.1 client to send a request without either a Content-Length: or Transfer-Encoding: Chunked header. I think it is still valid for a HTTP/1.0 client to connect to ohNet's 1.1 server and do this however (rfc2616 covers HTTP/1.1 only).

I think this means that your previous reports and suggested changes were valid. They could maybe be extended to confirm that only 1.0 requests assume read-request-until-disconnect. Unless you disagree, I'll add these tests.

Oh, and the original bug noted in this thread should be fixed and on github now Smile
Find all posts by this user


Messages In This Thread
RE: Problem when action request doesn't have Content-Length header - simonc - 04-07-2013 08:12 AM

Forum Jump: