Add content-length header for http2 connections#208
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Lukasa commented Mar 2, 2016
Thanks for this @natemara! The test troubles are interesting, I've got a suspicion they're timing related, but I'll try to take a look and see if I can fix them so that we can write some tests for this. |
Lukasa commented Mar 2, 2016
lily-mara commented Mar 2, 2016
Yes, I'm working on the development branch, with up to #205. |
Lukasa commented Mar 2, 2016
Hmm, that's perplexing. What's your environment? What Python are you using, what OpenSSL etc.? |
Lukasa commented Mar 23, 2016
@natemara Do you want to try rebasing onto the current development branch and try again? |
If a body is defined, we should be sending a Content-Length header unless the request has the Transfer-Encoding header is set. This should fix#206.
lily-mara commented Mar 24, 2016
Alright, that's rebased and checking now. |
Lukasa commented Mar 24, 2016
Ok, so this is doing better. There are two things that need to be solved:
Both of those will need to be fixed up. =) You up for doing that @natemara? |
| # Convert the body to bytes if needed. | ||
| ifbodyandisinstance(body, (unicode, bytes)): | ||
| body=to_bytestring(body) | ||
| if'Transfer-Encoding'notinheaders.keys(): |
There was a problem hiding this comment.
Any reason why we need O(n) here? Would it be better to just use:
if 'Transfer-Encoding' not in headers: .... 
michal-niklas left a comment
michal-niklas left a comment There was a problem hiding this comment.
With this change hyper can work with Jetty HTTP/2 server.
4 participants
If a body is defined, we should be sending a Content-Length header unless the request has the Transfer-Encoding header is set. This should fix#206. I was having some difficulty running the tests, but it seems like that was mostly related to SSL certificate problems. Looking at the spec doc, it says that clients SHOULD send the Content-Length header when there is no Transfer-Encoding header set.