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
Internet
Click on the red underlined text to get to the source
... HTTP/0.9, was a simple protocol for raw data transfer
across the Internet. HTTP/1.0, as defined by RFC 1945 [6 ...
... method is to be
applied. Messages are passed in a format similar to that used by
Internet mail as defined by the Multipurpose Internet Mail Extensions
(MIME ...
... applied. Messages are passed in a format similar to that used by
Internet mail as defined by the Multipurpose Internet Mail Extensions
(MIME).
...
... user agents and proxies/gateways to other Internet systems, including
those supported by the SMTP [16 ...
... preclude HTTP from being implemented on top of any other protocol on
the Internet, or on other networks. HTTP only presumes a reliable
...
... ANSI C's asctime() format
The first format is preferred as an Internet standard and represents
a fixed-length subset of that defined by RFC 1123std3 (an update ...
...
Media-type values are registered with the Internet Assigned Number
Authority (IANA). The media type registration process is outlined in
...
... HTTP/1.1 origin servers SHOULD be aware that the exact resource
identified by an Internet request is determined by examining both the
Request-URI and the Host ...
... HTTP servers
and causing congestion on the Internet. The use of inline images and
other associated data often requires a client ...
... Implementers should be aware that the software represents the user in
their interactions over the Internet, and should be careful to allow
the user to be aware of any actions they may take which may have an
unexpected significance to themselves or others.
...
...
The From request-header field, if given, SHOULD contain an Internet
e-mail address for the human user ...
... Internet e-mail address in this field MAY be separate from the
Internet host which issued the request. For example, when a request
is passed through a proxy ...
... The Host request-header field specifies the Internet host and port
number of the resource being requested, as obtained from the original
...
... header field in all HTTP/1.1 request
messages on the Internet (i.e., on any message corresponding to a
request for a URL which includes an Internet ...
... Internet (i.e., on any message corresponding to a
request for a URL which includes an Internet host address for the
...
... Host field to the request message prior
to forwarding it on the Internet. All Internet-based HTTP/1.1 servers
...
... request message prior
to forwarding it on the Internet. All Internet-based HTTP/1.1 servers
MUST respond with a 400 status code ...
... specification will help reduce past confusion over the relationship
between HTTP and Internet mail message formats.
The HTTP ...
... Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., Torrey, D., and B. Alberti. "The Internet Gopher Protocol: (a distributed document search and retrieval protocol)", RFC 1436 ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft, Innosoft, First Virtual, November 1996. ...
... Braden, R., "Requirements for Internet hosts - application and support", STD 3, RFC 1123std3 ...
... Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822std11(-> 2822prop) ...
... Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047draft ...
... Internet Media Type message/http ...
... In addition to defining the HTTP/1.1 protocol, this document serves
as the specification for the Internet media type "message/http". The
following is to be registered with IANA ...
... Internet Media Type multipart/byteranges ...
...
HTTP/1.1 uses many of the constructs defined for Internet Mail (RFC
822) and the Multipurpose Internet Mail Extensions (MIME ...
... HTTP/1.1 uses many of the constructs defined for Internet Mail (RFC
822) and the Multipurpose Internet Mail Extensions (MIME ) to allow
entities to be transmitted in an open variety of representations and
...
...
MIME requires that an Internet mail entity be converted to canonical
form prior to being transferred. Section 3.7.1 of this document
...
... experimental
applications of Content-Type for Internet mail have used a media-type
parameter of ";conversions=<content-coding>" to perform an equivalent
...
... IP address
to which that request was directed. The changes outlined above will
allow the Internet, once older HTTP clients are no longer common, to
support multiple Web sites ...
... host has created serious problems. The
Internet will also be able to recover the IP addresses that have been
allocated for the sole purpose of allowing special-purpose domain
names ...