Beruflich Dokumente
Kultur Dokumente
HTTP Protocol
Introduction to HTTP
Controller
Clients
Interpreter
Request Chain
TCP Connection
Response Chain
User Agent
Origin Server
Request Chain
A B C
Response Chain
User Agent
Origin Server
Inter-
TCP connection Proxy mediary
User Agent
Origin Server
There are two scenarios that call for the use of a proxy:
Security intermediary: the client and server may be separated by a
security intermediary such as a firewall with the proxy is on the client
side of the firewall. Typically, the client is part of a network secured by
a firewall and the server on is external to the secured network. To set
up a connection with the proxy, the server has to authenticate itself with
the firewall. The proxy accepts responses after they have passed
through the firewall.
Different versions of HTTP: if the client and server are running different
versions of HTTP, then the proxy can implement both versions and
perform the required mapping.
Intermediary
TCP connection Gate-
way
User Agent
Origin Server
There are two scenarios that call for the use of a gateway:
Security intermediary: the client and server may be separated by a
security intermediary such as a firewall with the gateway on the server
side of the firewall. Typically, the server is connected to a network
protected by a firewall, with the client external to the network. In this
case, the client must authenticate itself to the proxy, which can then
pass the request on to the server.
Non-HTTP server: useful when Web browsers need to contact servers
for protocols other than HTTP, such as FTP. The client makes an HTTP
request to a gateway server. The gateway server then contacts the
relevant FTP server to obtain the desired result. This result is then
converted to a form suitable for HTTP and transmitted back to the
client.
User Agent
Origin Server
A B C
Response
User Agent Chain
Origin Server