This article will cover the following topics:
An overview of the basics of HTTP
What is HTTP pipelining?
What problems can appear with HTTP pipelining?
Why you should care about HTTP pipelining?
Which web servers support HTTP pipelining?
Which browsers support HTTP pipelining? (And how to enable it)
Which programming languages/libraries support HTTP pipelining?
An overview of the basics of HTTP
The HTTP protocol works by sending requests and getting responses back for those requests.
I will not get into the details of the HTTP protocol syntax. Details about headers, HTTP methods, paths, parameters, etc., as this post would be too long. Instead I'll just cover some basics and then dive right into explaining HTTP pipelining. But I will show a basic HTTP GET request and response.
A typical HTTP request looks something like this:
GET / HTTP/1.1
Host: www.brianbondy.com
User-Agent: Mozilla/5.0
Connection: keep-alive
A typical HTTP response looks something like this:
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Server: Google Frontend
Content-Length: 12100
...content...
Read more: Brian R. Bondy
Posts
0 comments:
Post a Comment