Using the wrong HTTP 1.0 practice?

I am implementing a basic http client for communicating with a web service, and I am wondering if I should go with http 1.0 or 1.1. The data section will consist of binary data, and the remote server will always be controlled by me (works with IIS7.5). Firewalls / proxies between them do not control anything, i.e. packets should not stop if the wrong version of http is being used.

I read about the difference between http 1.0 and 1.1 , and it seems to me that http 1.0 supports everything I need.

Will I run into problems if I choose http 1.0 for 1.1 or can I assume that everything will work just as well?

Interestingly, if I connect via raw sockets to IIS7.5 and send a request for http 1.0, the response is always http 1.1.

+3
source share
2 answers

The firewall, of course, will not block it, and the router will route it.

I would suggest using HTTP 1.1. Most likely, nothing will affect if you use HTTP 1.0. However, you never know who else might use your HTTP client in the future and what a terrible server implementation it will use.

You also need to ask yourself why you are using the HTTP client in the first place. Why not just use the standard library? I don’t know which language you use, but libcurlhas bindings for many languages.

Read more about libcurl here .

+1
source

I do not think that something is wrong, using 1.0 as a client, most web servers are backward compatible.

, 1.1, , , , - , .

+1

All Articles