#HTTP1.0 #Vs HTTP1.1
What is Http1.0 | What is Http1.1 ► SUBSCRIBE & LIKE!!
► Important Information and code guide available bottom of the Description section
► Official Email Id: techtalk.debu@gmail.com
► Download the sample java microservice application :
[ Ссылка ]
► Follow on Facebook: [ Ссылка ]
► Follow on LinkedIn: [ Ссылка ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
► Here is our amazing playlist for Core Java, Spring MVC/Boot, Git and Micro service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Core Java :: [ Ссылка ]
2. Core Java Important Interview QA : [ Ссылка ]
3. Spring MVC & Spring Boot :: [ Ссылка ]
4. Micro Services :: [ Ссылка ]
5. Git/GitHub :: [ Ссылка ]
6. AWS :: [ Ссылка ]
7. Spring Security & OAuth : [ Ссылка ]
8. Coding and Programming : [ Ссылка ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Watch my "Most Watched Videos"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
► HTTPS & HTTPS protocol :: [ Ссылка ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A major difference between HTTP/1.0 and HTTP/1.1 is that HTTP/1.0 uses a new connection for each request/response exchange,
where as HTTP/1.1 connection may be used for one or more request/response exchanges.
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.
HTTP 1.1 generally an upgrade of limitations of HTTP 1.0
HTTP 1.0 can define 16status codes
HTTP 1.1 can define 24 status codes
HTTP 1.1 has a warning header capable of producing many secondary status alerts
HTTP 1.0 authentication unsafe as it is not encrypted
HTTP 1.1 safe as it uses a checksum of username, password, and one-time value.
Thanks & Regards,
Debu Paul
![](https://i.ytimg.com/vi/dMlzvnaWgy8/maxresdefault.jpg)