HTTP 1.0 vs 1.1

by

Proxy support and the Host field:

HTTP 1.1 has a required Host header by spec.

HTTP 1.0 does not officially require a Host header, but it doesn’t hurt to add one, and many applications (proxies) expect to see the Host header regardless of the protocol version.

Example:

GET / HTTP/1.1
Host: www.blahblahblahblah.com

This header is useful because it allows you to route a message through proxy servers, and also because your web server can distinguish between different sites on the same server.

So this means if you have blahblahlbah.com and helohelohelo.com both pointing to the same IP. Your web server can use the Host field to distinguish which site the client machine wants.

Persistent connections:

HTTP 1.1 also allows you to have persistent connections which means that you can have more than one request/response on the same HTTP connection.

In HTTP 1.0 you had to open a new connection for each request/response pair. And after each response the connection would be closed. This lead to some big efficiency problems because of TCP Slow Start.

OPTIONS method:

HTTP/1.1 introduces the OPTIONS method. An HTTP client can use this method to determine the abilities of the HTTP server. It’s mostly used for Cross Origin Resource Sharing in web applications.

Caching:

HTTP 1.0 had support for caching via the header: If-Modified-Since.

HTTP 1.1 expands on the caching support a lot by using something called ‘entity tag’.
If 2 resources are the same, then they will have the same entity tags.

HTTP 1.1 also adds the If-Unmodified-Since, If-Match, If-None-Match conditional headers.

There are also further additions relating to caching like the Cache-Control header.

100 Continue status:

There is a new return code in HTTP/1.1 100 Continue. This is to prevent a client from sending a large request when that client is not even sure if the server can process the request, or is authorized to process the request. In this case the client sends only the headers, and the server will tell the client 100 Continue, go ahead with the body.

Much more:

  • Digest authentication and proxy authentication
  • Extra new status codes
  • Chunked transfer encoding
  • Connection header
  • Enhanced compression support
  • Much much more.

More Related Contents:

  1. What is the maximum length of a URL in different browsers?
  2. Do I need Content-Type: application/octet-stream for file download?
  3. What requests do browsers’ “F5” and “Ctrl + F5” refreshes generate?
  4. CORS with POSTMAN
  5. URL matrix parameters vs. query parameters
  6. What is idempotency in HTTP methods?
  7. Is there a practical HTTP Header length limit?
  8. Why do I need to use http.StripPrefix to access my static files?
  9. What is httpinterceptor equivalent in angular2?
  10. How to make external HTTP requests with Node.js [closed]
  11. Golang read request body multiple times [duplicate]
  12. What is the difference between HTTP_CLIENT_IP and HTTP_X_FORWARDED_FOR?
  13. What is the difference between PUT, POST and PATCH?
  14. What’s the difference between a 302 and a 307 redirect?
  15. Should I URL-encode POST data?
  16. Why am I getting “(304) Not Modified” error on some links when using HttpWebRequest?
  17. Difference between Content-Range and Range headers?
  18. How are cookies passed in the HTTP protocol?
  19. HTTP POST request in Inno Setup Script
  20. URL hash is persisting between redirects
  21. nginx close upstream connection after request
  22. Official references for default values of concurrent HTTP/1.1 connections per server? [closed]
  23. Does the HTTP Protocol support multiple content types in response headers?
  24. What is the http-header “X-XSS-Protection”?
  25. What is correct HTTP status code when redirecting to a login page?
  26. How to cancel a HTTPRequest in Angular 2?
  27. Sending browser cookies during a 302 redirect
  28. Correctly switching between HTTP and HTTPS using .htaccess
  29. Is a URL with // in the path-section valid?
  30. How to set up CORS or OPTIONS for Rocket.rs

Leave a Comment