Skip to content
New issue

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

Allow to send HTTP/1.0 response ? #50

Closed
paneq opened this issue Sep 1, 2012 · 3 comments
Closed

Allow to send HTTP/1.0 response ? #50

paneq opened this issue Sep 1, 2012 · 3 comments

Comments

@paneq
Copy link
Collaborator

paneq commented Sep 1, 2012

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 ?

@mostlyobvious
Copy link
Collaborator

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)?

@paneq
Copy link
Collaborator Author

paneq commented Sep 3, 2012

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 ?

@mostlyobvious
Copy link
Collaborator

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.

@paneq paneq closed this as completed Nov 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants