1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
gateway
Click on the red underlined text to get to the source
... user agents and proxies/gateways to other Internet systems, including
those supported by the SMTP ...
... in general. Likewise, any server may act as an origin server,
proxy, gateway, or tunnel, switching behavior based on the nature
of each request.
...
... requirements of this specification.
gateway
A server which acts as an intermediary for some other server.
Unlike a proxy, a gateway ...
... gateway
A server which acts as an intermediary for some other server.
Unlike a proxy, a gateway receives requests as if it were the
origin server for the requested resource; the requesting client
...
... origin server for the requested resource; the requesting client
may not be aware that it is communicating with a gateway.
tunnel ...
... request/response chain. There are three common
forms of intermediary: proxy, gateway, and tunnel. A proxy is a
...
... rewriting all or part of the message, and forwarding the reformatted
request toward the server identified by the URI. A gateway is a
receiving agent, acting as a layer ...
...
Proxy and gateway applications must be careful when forwarding
messages in protocol versions different from that of the application.
...
... sender, a proxy/gateway MUST never send a message with a version
indicator which is greater than its actual version ...
... version request is received, the proxy/gateway MUST either downgrade
the request version, respond with an error, or switch ...
... version lower than that of the
proxy/gateway's version MAY be upgraded before being forwarded; the
proxy ...
... version MAY be upgraded before being forwarded; the
proxy/gateway's response to that request MUST be in the same major
version as the request.
...
... applications, as is sometimes the case when retrieving or posting
messages via proxies/gateways to SMTP or NNTP.
...
... The most common form of Request-URI is that used to identify a
resource on an origin server or gateway. In this case the absolute
path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
...
... | "500" ; Internal Server Error
| "501" ; Not Implemented
| "502" ; Bad Gateway
| "503" ; Service Unavailable ...
... POST request identifies the resource that will handle the enclosed
entity. That resource may be a data-accepting process, a gateway to
some other protocol, or a separate entity that accepts annotations.
...
... entity-body of a 200 (OK) response. The final recipient is either the
origin server or the first proxy or gateway to receive a Max-Forwards
value of zero (0) in the request (see section 14.31). A TRACE request
...
... Bad Gateway ...
...
The server, while acting as a gateway or proxy, received an invalid
response from the upstream ...
... Gateway Timeout ...
...
The server, while acting as a gateway or proxy, did not receive a
timely response from the upstream ...
... Cache directives must be passed through by a proxy or gateway
application, regardless of their significance to that application,
since the directives may be applicable to all recipients along the
...
... either respond using a cached entry that is consistent with the other
constraints of the request, or respond with a 504 (Gateway Timeout)
status. However, if a group of caches ...
... particular, if the cache cannot reach the origin server for any
reason, it MUST generate a 504 (Gateway Timeout) response.
Servers should send the must-revalidate directive if and only if
...
... header field; proxies and
gateways MUST NOT generate it, as this would defeat its value as an
end-to-end integrity check. Any recipient of the entity ...
... end-to-end integrity check. Any recipient of the entity-body,
including gateways and proxies, MAY check that the digest value in
this header field ...
... Host field value MUST represent
the network location of the origin server or gateway given by the
original URL. This allows the origin server or gateway ...
... gateway given by the
original URL. This allows the origin server or gateway to
differentiate between internally-ambiguous URLs, such as the root ...
... of the set of last-modify times for its component parts. For database
gateways, it may be the last-update time stamp of the record. For
...
... method (section 14.31) to limit the number of proxies or gateways
that can forward the request to the next inbound server. This can be
useful when the client ...
...
Pragma directives MUST be passed through by a proxy or gateway
application, regardless of their significance to that application,
since the directives may be applicable to all recipients along the
...
...
The Via general-header field MUST be used by gateways and proxies to
indicate the intermediate protocols and recipients between the user
agent ...
...
Multiple Via field values represent each proxy or gateway that has
forwarded the message. Each recipient MUST append its information
such that the end result is ordered according to the sequence of
...
... header field to identify the software
of the recipient proxy or gateway, analogous to the User-Agent and
Server header fields ...
... host containing information protected by basic authentication when in
fact he is connecting to a hostile server or gateway then the
attacker can request a password ...
... 32]. Server implementers SHOULD guard against the possibility of
this sort of counterfeiting by gateways or CGI scripts. In particular
it is very dangerous for a server to simply turn over a connection ...
... it is very dangerous for a server to simply turn over a connection to
a gateway since that gateway can then use the persistent connection
...
... connection to
a gateway since that gateway can then use the persistent connection
mechanism to engage in multiple transactions ...
... MIME.
Proxies and gateways to strict MIME environments SHOULD be aware of
these differences and provide the appropriate conversions where
...
... these differences and provide the appropriate conversions where
necessary. Proxies and gateways from MIME environments to HTTP also
...
... simplify the process of date comparison. Proxies and gateways from
other protocols SHOULD ensure that any Date header field present in a
...
... Encoding header field. Since this acts as a modifier on the media
type, proxies and gateways from HTTP to MIME-compliant protocols MUST
...
... transport" is defined by the limitations of the protocol being used.
Such a proxy or gateway SHOULD label the data with an appropriate
Content-Transfer-Encoding if doing so will improve the likelihood of
...
... header field (section
14.40). Proxies/gateways MUST remove any transfer coding prior to
forwarding a message via a MIME-compliant ...
... MIME protocol.
Proxies/gateways are responsible for ensuring full compliance (where
possible) when exporting HTTP messages to strict MIME ...