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
transport
Click on the red underlined text to get to the source
... connection
A transport layer virtual circuit established between two programs
for the purpose of communication.
...
... networks. HTTP only presumes a reliable
transport; any protocol that provides such guarantees can be used;
the mapping of the HTTP/1.1 request and response ...
... HTTP/1.1 request and response structures onto the
transport data units of the protocol in question is outside the scope
of this specification.
...
... transformation that has been, can be, or may need to be applied to an
entity-body in order to ensure "safe transport" through the network.
This differs from a content coding in that the transfer coding is a
...
... Content-Transfer-Encoding
values of MIME , which were designed to enable safe transport of
binary data over a 7-bit ...
... binary data over a 7-bit transport service. However, safe transport
has a different focus for an 8bit ...
... binary data over a 7-bit transport service. However, safe transport
has a different focus for an 8bit-clean transfer protocol. In HTTP ...
... determining the exact body length (section 7.2.2), or the desire to
encrypt data over a shared transport.
The chunked encoding ...
... HTTP relaxes this requirement and allows the
transport of text media with plain CR or LF alone representing a line
break ...
... proxy servers) that it
connects to. Each persistent connection applies to only one transport
link.
...
... When a client or server wishes to time-out it SHOULD issue a graceful
close on the transport connection. Clients and servers SHOULD both
constantly watch for the other side of the transport ...
... transport connection. Clients and servers SHOULD both
constantly watch for the other side of the transport close, and
respond to it as appropriate. If a client or server does not detect
...
... A client, server, or proxy MAY close the transport connection at any
time. For example, a client MAY have started to send a new request at
...
... asynchronous close events. Client software SHOULD reopen the
transport connection and retransmit the aborted request without user
interaction so long as the request method is idempotent (see section
...
... error status. If it responds with an
error status, it MAY close the transport (TCP) connection or it MAY
...
... access authentication. Additional
mechanisms MAY be used, such as encryption at the transport level or
via message encapsulation, and with additional header ...
... o Hop-by-hop headers, which are meaningful only for a single
transport-level connection, and are not stored by caches or
...
... header field only applies to switching application-layer
protocols upon the existing transport-layer connection. Upgrade
cannot be used to insist on a protocol change; its acceptance and use
...
... responsible for ensuring that the message is in the correct format
and encoding for safe transport on that protocol, where "safe
transport" is defined by the limitations of the protocol being used.
...
... encoding for safe transport on that protocol, where "safe
transport" is defined by the limitations of the protocol being used.
Such a proxy or gateway ...
... Content-Transfer-Encoding if doing so will improve the likelihood of
safe transport over the destination protocol.
...