HTTP/1.1 supports pipelining - multiple related requests are written to a single TCP socket without waiting for the resp

Business, Finance, Economics, Accounting, Operations Management, Computer Science, Electrical Engineering, Mechanical Engineering, Civil Engineering, Chemical Engineering, Algebra, Precalculus, Statistics and Probabilty, Advanced Math, Physics, Chemistry, Biology, Nursing, Psychology, Certifications, Tests, Prep, and more.
Post Reply
answerhappygod
Site Admin
Posts: 899604
Joined: Mon Aug 02, 2021 8:13 am

HTTP/1.1 supports pipelining - multiple related requests are written to a single TCP socket without waiting for the resp

Post by answerhappygod »

HTTP/1.1 supports pipelining - multiple related requests are written to a single TCP socket without waiting for the responses to come back i.e. the requests are done asynchronously in-parallel, instead of doing them sequentially as usual (see picture). Some Web clients such as Opera and Firefox with FasterFox plugin use HTTP pipelining. Assume that ProxySG Is deployed as a forward proxy listening on port 8080.

A. If an HTTP client tries to use pipelining, the use of proxy will break the HTTP protocol.
B. For those HTTP clients that use pipelining, the use of forward proxy would ensure faster response time compared to the clients that do not use pipelining.
Join a community of subject matter experts. Register for FREE to view solutions, replies, and use search function. Request answer by replying!

This topic has 1 reply

You must be a registered member and logged in to view the replies in this topic.


Register Login
 
Post Reply