Menu
Is it alright to respond with HTTP/1.0 to HTTP/1.1 request?
I am implementing HTTP communication through simple sockets and clients make requests with both HTTP/1.0 and HTTP/1.1 but protocol is independent of HTTP version so I want to always respond with HTTP/1.0 to all requests. Does HTTP standard bear such communication?
535
This specification defines the protocol referred to as "HTTP/1.1". This protocol is backwards-compatible with HTTP/1.0, but includes more stringent requirements in order to ensure reliable implementation of its features.
A small number of mobile applications still use HTTP 1.0. This early version of the HTTP protocol doesn't support improvements, like persistent TCP connections, that make HTTP 1.1 much more efficient to use.
The first usable version of HTTP was created in 1997. Because it went through several stages of development, this first version of HTTP was called HTTP/1.1. This version is still in use on the web.
HTTP2 is much faster and more reliable than HTTP1. HTTP1 loads a single request for every TCP connection, while HTTP2 avoids network delay by using multiplexing. HTTP is a network delay sensitive protocol in the sense that if there is less network delay, then the page loads faster.
Of course it's alright. Otherwise, if you only supported HTTP/1.0, what could you do?
If HTTP 1.2 came out today, what do you think all existing HTTP 1.1 servers would send as replies to HTTP 1.2 queries? Of course, it'll have to be HTTP 1.1 replies -- that's all they know how to do.
Just make sure you don't follow HTTP 1.1 rules where they differ. For example, keep alives are not enabled by default. If a client sees an HTTP 1.0 reply, it will assume HTTP 1.0 semantics.
183
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
