HTTP/1.1 supports pipelining - multiple related requests are written to a single TCP socket without waiting for the resp
Posted: Fri Jul 22, 2022 11:27 am
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.
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.