We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently our responses are HTTP/1.1 hardcoded. What if framework working on top of our library is HTTP/1.0 compatible only ? Is that possible ?
HTTP/1.1
HTTP/1.0
The text was updated successfully, but these errors were encountered:
Although not explicitly stated in features, should be possible. That probably boils down to keep-alives and explicitly closing connection by handler.
More on this topic: http://librelist.com/browser//mongrel2/2012/3/2/mongrel2-and-http-headers/#5dda3ad796ff5fc73fb6b75a9932105c
@paneq What's the benefit of supporting RFC predating HTTP/1.1 (which is 13 years old)?
Sorry, something went wrong.
So basically #43 ?
@pawelpacana I am not sure. That's why there is ? in the ticket. Are there still some serious clients using 1.0 ?
?
Maybe let's check how popular mobile clients present themself since in logs of one of my application I observe lots of HTTP/1.0.
Initial (failing) version of fix for #43 #50
6abc359
No branches or pull requests
Currently our responses are
HTTP/1.1
hardcoded. What if framework working on top of our library isHTTP/1.0
compatible only ? Is that possible ?The text was updated successfully, but these errors were encountered: