R. Fielding, J. Gettys, J. Mogul, H. Frystyk, and T. Bernes-Lee, "Hypertext transfer protocol -- HTTP/1.1," Internet Request for Comments RFC  Home/Search   Document Not in Database   Summary   Related Articles   Check

....reduced by TCP s slow start mechanism. A 2 kilobyte file has a throughput of less than 10 of the best case. They propose additions to HTTP that would allow it to send several files over a single connection, thus avoiding these obstacles. This concept has been adopted in the proposed HTTP 1. 1 [5]. Their proposal also utilizes pipelining; a client may request the next file before the current file has completed. Thus, there would be no gaps between consecutive files. They report that their changes reduce latency by more than half when transferring 2544 byte inline images. Bartlett ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk and T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1," RFC

....the updated object is returned as a regular response. The server can also add an Expires header to indicate when the object should expire from the cache and be re validated. in practice this header is difficult to use because it is hard to predict when an object will next be modified. HTTP 1. 1 [12] adds mechanisms to allow clients, proxy caches, and origin servers to control caching policy. These headers can identify the maximum staleness allowed for an object (how old an object can be served from cache without validation) the minimum freshness (again, how old) the maximum age (how ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, "Hypertext Transfer Protocol - - HTTP/1.1", IETF RFC 2616, June 1999. The Internet Society.

....from the server consists of ranges of the original file; thus, the server need not have any special knowledge of the QSplat file format. In our implementation of the streaming QSplat client we have chosen to use the HTTP 1. 1 protocol (including the byte range and persistent connection features [Fielding 97] to issue requests, so we may stream models from any standard web server (e.g. Apache) a separate streaming server is not required. 3.6 Discussion Let us now examine some of the advantages and disadvantages involved in using QSplat, as compared to traditional polygonal representations, as the ....

Fielding,R.,Gettys,J.,Mogul,J.,Frystyk,H.,Berners-Lee,T. "Hypertext Transfer Protocol -- HTTP/1.1," RFC

....a Record Route (Section 10.34) header field. 1.4 Definitions This specification uses a number of terms to refer to the roles played by participants in SIP communications. The definitions of client, server and proxy are similar to those used by the Hypertext Transport Protocol (HTTP) RFC 2616 [8]) The terms and generic syntax of URI and URL are defined in RFC 2396 [9] The following terms have special significance for SIP. Back To Back User Agent: Also known as a B2BUA, this is a logical entity that receives an invitation, and acts as a UAS to process it. In order to determine how the ....

....deprecated. Except for the above difference in character sets and line termination, much of the message syntax is and header fields are identical to HTTP 1.1; rather than repeating the syntax and semantics here we use [HX.Y] to refer to Section X.Y of the current HTTP 1. 1 specification (RFC 2616 [8]) In addition, we describe SIP in both prose and an augmented Backus Naur form (ABNF) See section C for an overview of ABNF. Note, however, that SIP is not an extension of HTTP. Unlike HTTP, SIP MAY use UDP or other unreliable datagram protocols. Each such datagram carries one request or ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, "Hypertext transfer protocol -- HTTP/1.1," Request for Comments 2616, Internet Engineering Task Force, June 1999.

....it may use a connectionless transport protocol such as UDP. The streams controlled by RTSP may use RTP [1] but the operation of RTSP does not depend on the transport mechanism used to carry continuous media. The protocol is intentionally similar in syntax and operation to HTTP 1. 1 [2] so that extension mechanisms to HTTP can in most cases also be added to RTSP. However, RTSP differs in a number of important aspects from HTTP: ffl RTSP introduces a number of new methods and has a different protocol identifier. ffl An RTSP server needs to maintain state by default in almost ....

....(There is an exception to this. ffl RTSP is defined to use ISO 10646 (UTF 8) rather than ISO 8859 1, consistent with current HTML internationalization efforts [3] ffl The Request URI always contains the absolute URI. Because of backward compatibility with a historical blunder, HTTP 1. 1 [2] carries only the absolute path in the request and puts the host name in a separate header field. This makes virtual hosting easier, where a single host with one IP address hosts several document trees. The protocol supports the following operations: Retrieval of media from media server: The ....

[Article contains additional citation context not shown here]

R. Fielding, J. Gettys, J. Mogul, H. Nielsen, and T. Berners-Lee, "Hypertext transfer protocol -- HTTP/1.1," RFC

....via a Record Route (Section 6.35) header field. 1.4 Definitions This specification uses a number of terms to refer to the roles played by participants in SIP communications. The definitions of client, server and proxy are similar to those used by the Hypertext Transport Protocol (HTTP) RFC 2616 [8]) The terms and generic syntax of URI and URL are defined in RFC 2396 [9] The following terms have special significance for SIP. Call: A call consists of all participants in a conference invited by a common source. A SIP call is identified by a globally unique call id (Section 6.13) Thus, if a ....

....deprecated. Except for the above difference in character sets and line termination, much of the message syntax is and header fields are identical to HTTP 1.1; rather than repeating the syntax and semantics here we use [HX.Y] to refer to Section X.Y of the current HTTP 1. 1 specification (RFC 2616 [8]) In addition, we describe SIP in both prose and an augmented Backus Naur form (ABNF) See section C for an overview of ABNF. Note, however, that SIP is not an extension of HTTP. Unlike HTTP, SIP MAY use UDP or other unreliable datagram protocols. Each such datagram carries one request or ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, "Hypertext transfer protocol -- HTTP/1.1," Request for Comments 2616, Internet Engineering Task Force, June 1999.

....TCP flow export records which have the FIN bit set can be used to determine TCP performance to those flows client destination hosts. We consider other pertinent aspects of NetFlow s representation of HTTP streams below. A. Persistent Connections HTTP allows and encourages persistent connections [8]. A consequence of this is that the duration of HTTP TCP streams is often longer than the maximum flow duration which we configured to be one minute. Therefore, multiple flows are often required to record the entire lifetime of the stream. That is, many TCP flows are not atomic since a single flow ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, "Hypertext transfer protocol -- http/1.1," IETF RFC 2616, June 1999.

....the satellite whenever enabled. Our study consists of six main scenarios: splitting enabled or disabled with cache hit or cache miss and the option of whether to bypass the cache or not, as shown in Figure 3. Whether to use the file in the cache or not is controlled by a no cache pragma [21] [22] sent in the request header. When set, this parameter tells the cache not to use the cached copy even if there is one and to get the most updated version from the server. Whether the connection splitting proxy used or not is controlled by the end hosts. We have two end hosts, one of which has the ....

....we expect to see a lower performance gain. It should be noted that the measurements in Tables III and IV are taken over different time periods and thus numbers from different tables are not directly comparable. Next we explore the performance comparison between using HTTP 1.0 and HTTP 1. 1 [22]. Web browsers are typically configured to use HTTP 1.0 in the proxy mode where a separate connection is established for each embedded object on a page. HTTP 1.0 generally results in large delay due to the time spent in hand shaking and low throughput in the slow start phase of TCP. HTTP 1.1 on ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyc, and Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1," IETF RFC

....recipient s computer system. Specifically, the email content retrieved by the Web browser must not be left in any cache in clear text. Two schemes are employed to pursue this objective. 1. Whenever returning the email content, the personal server always put a Cache Control: no store directive [24] or a Pragma: no cache directive [25] in the head part of the HTTP response message. Thus, Web caches and Web browsers compliant with the HTTP protocols won t cache the email content. 2. The email content is returned to the Java applet after being encrypted by a disposable secret key. The ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", IETF RFC 2616, Jun. 1999.

....head of line blocking. HTTP 1.0 [10] will start a separate, dedicated TCP connection for every web transaction. Thus, during page retrieval, a bundle of concurrent TCP connections is active between client and server. Persistent connection HTTP (P HTTP) 24] which has been included in HTTP 1. 1 [9] since being proposed, allows multiple HTTP transactions to take place sequentially over one TCP connection. However, most clients still open more than one persistent connection to a server to speed up initial page rendering. Due to the nature of the TCP congestion control algorithms, a bundle of ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. "Hypertext Transfer Protocol - HTTP/1.1." Work In Progress (Internet Draft draft-ietfhttp -v11-spec-rev-06). November 1998.

....its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred [15]. The format of a typical HTTP request response is as follows 1. A client opens a connection with a server. 2. The client sends a request to the server. This request consists of a request method, URI, and protocol version, followed by a MIME like message containing request modifiers, client ....

....to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or nontransparent behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies [15]. Although proxies provide various capabilities that improve the end user experience with features such as caching, they are examined in this dissertation for the ability to analyse HTTP request and response information for requests that are directed through them. 2.5.3.1 Performance ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. BernersLee, "Hypertext Transfer Protocol -- HTTP/1.1 " : The Internet Society, June 1999; http://www.ietf.org/rfc/rfc2616.txt

....This allows unsecured and secured HTTP traffic to share the same well known port (in this case, http: at 80 rather than https: at 443) It also enables virtual hosting , so a single HTTP TLS server can disambiguate traffic intended for several hostnames at a single IP address. Since HTTP 1. 1 [1] defines Upgrade as a hop by hop mechanism, this memo also documents the HTTP CONNECT method for establishing end toend tunnels across HTTP proxies. Finally, this memo establishes new IANA registries for public HTTP status codes, as well as public or private Upgrade product tokens. This memo ....

....and reassembly for the remainder of the connection. The latter is intended to be completely transparent. For example, there is no dependency between TLS s record markers and or certificates and HTTP 1.1 s chunked encoding or authentication. Either the client or server can use the HTTP 1. 1 [1] Upgrade mechanism (Section 14.42) to indicate that a TLS secured connection is desired or necessary. This memo defines the TLS 1.0 Upgrade token, and a new HTTP Status Code, 426 Upgrade Required . Section 3 and Section 4 describe the operation of a directly connected client and server. ....

[Article contains additional citation context not shown here]

Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

....(see section 4.3) New connections can be distributed either randomly, load dependent, or dependent on information inside the datagram. Another example for a decentralized distribution depends on the cooperation between client and server: Example: Redirecting HTTP requests The HTTP protocol [Fielding et al. 97] enables servers to redirect requests by sending the clients an alternative URL. This feature can be used by parallel servers to balance their load. Whenever a server under heavy load receives a request it may decide to redirect the request to a replicated server. An obvious problem with this ....

Roy T. Fielding, Jim Gettys, Jeffrey C. Mogul, Henrik Frystyk Nielsen, Tim Berners-Lee. "Hypertext Transfer Protocol -- HTTP/1.1". RFC 2068, January 1997. (ftp://ds.internic.net/rfc/rfc2068.txt)

....the client cannot always determine which certificates are needed to link the cache s public key to one of the keys mentioned in the ACL. One vital issue is how the cache can send this security information to the client in a manner that does not confuse legacy clients. Note that standard HTTP 1. 1 [9] headers already contain the date, the cache name, and the URL. Further, the client computes the hash of the request itself. All the cache needs to send are the ACL, the signature, and certificates. We include these three items in the HTTP 1.1 Pragma header field. The HTTP specification states ....

....features of HTTP 1.1. Unfortunately, at least one widely deployed brand of web cache does not implement the features of HTTP on which this method relies. Therefore, we also present a second method which should work with every cache. A. Discovering Gemini documents via HTTP The HTTP 1. 1 standard [9] allows a single URL to stand for multiple versions of the same document. This allows a server to offer a document in different languages (English, French, or Russian) or with a different encoding (JPEG or GIF; compressed, gzip d, or without compression) We can use this feature to distribute ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, "Hypertext transfer protocol -- HTTP/1.1," IETF RFC 2616, June 1999, Available at http://www.ietf.org/rfc/rfc2616.txt.

....information from the web, such as keyword filtering and email updates. The service is location independent since it is located on a Web server, and can therefore be accessed from any location with Internet access. Any terminal can be used to access the service if it can communicate using HTTP [Bren Lee], and understand HTML. This implies that the service is browser independent . II. SOFTWARE AGENTS AND INFORMATION RETRIEVAL Software agents are autonomous programs that can perform tasks and operations on behalf of a user. Agents can either be stationary or mobile. A stationary agent performs ....

Fielding, R., Gettys, J., Mogul, J.C., Frystyk, H., Masinter, L., Leach, P., and Breners-Lee, T.: `Hypertext Transfer Protocol -- HTTP/1.1', The Internet Society and The Internet Engineering Task Force, RFC 2616.

....or integrate policies based on object popularity. Our work formalizes the issues and policies and systematically evaluates them. III. FRESHNESS CONTROL We provide a simplified overview of the freshness control mechanism specified by HTTP and supported by compliant caches. For further details see [28], 29] 10] 30] 31] Caches compute for each object a time to live (TTL) value during which it is considered fresh and beyond which it becomes stale. When a request arrives for a stale object, the cache must validate it before serving it, by communication either with an entity with a fresh ....

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, and T. Leach, P. Berners-Lee, "Hypertext Transfer Protocol --- HTTP/1.1," RFC 2616, ISI, June 1999.

....as generic gateways between the webserver and the object model of the database. The approach in Fig 6 was pioneered by the ANSAweb proposal [10] The ANSAweb code treated all resources with URLs [11] preceded by http: implying they were accessible by hypertext transfer protocol (HTTP) [12]) as potentially reachable with CORBA IIOP. The aim was to decouple the URL from the choice of transfer protocol. Ignoring the desire for this particular abstraction it is H aving discussed three of the most influential distributed object models in the previous section, we now arrive at the core ....

Fielding R et al: `Hypertext Transfer Protocol --- HTTP/1.1', RFC2068 (August 1996), http://ds.internic.net/rfc/rfc2068.txt

....three components: 1) the server software, 2) the client software and 3) the HTTP protocol. The information that is written to the log depends on the server software and also the parameters that are sent by the browser. The information exchange is done within the capabilities of the HTTP protocol [4]. A typical httpd log contains (example taken from the documentation of one of the most popular WWW servers, apache (http: www.apache.org ) host ident authuser date request status bytes where the tokens are ffl host The fully qualified domain name of the client, or its IP number if the name ....

Fielding, R., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, January 1997. ftp://ftp.isi.edu/in-notes/rfc2068.txt

....the number of active sources. Routers inside the network perform scheduling with a simple weighted round robin scheduler by servicing each queue according to a prespecified weight. To generate web traffic on the application level, we explicitly model the request and reply interactions of HTTP 1. 1 [10]. The reply objects (index object and embedded objects) are generated with sizes according to statistical distributions determined by web crawling. Same for the number of embedded objects. We also use statistics to model server selection and think time (inter page time) Underneath HTTP, we use ....

R. Fielding et. al., "Hypertext transfer protocol --- http/1.1," RFC 2616, Internet Request For Comments, June 1999.

....overhead is present. Given the WWW classic access pattern described in the previous section, since the client must wait for the server to send its connection response, an overhead is added in terms of time spent waiting. The solution to this problem can be the Keep Alive facility as described in [8]. The Keep Alive facility allows different requests to be sent over a single V.Trecordi and A. Verga An Experimental Study on the Performance of WWW Servers 6 connection reducing the set up and tear down overhead. Improvement to these issues are being proposed by the HTTP Next Generation (HTTP NG) ....

....On Solaris 2.4 and 2.5 this parameter can be changed, without recompiling the kernel, up to a maximum value of 32 and 1024 respectively. Another component affecting the performance of the TCP IP protocol stack is the permanence time in the TCP TIME WAIT state of the protocol finite state machine [8]. When a server closes a TCP connection it keeps the information associated to that connection for a fixed amount of time. As a V.Trecordi and A. Verga An Experimental Study on the Performance of WWW Servers 8 consequence a server will keep system s resources for every connection for a certain ....

R. Fielding, H.Frystyk, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", HTTP Working Group, Internet draft, 1995.

No context found.

R. Fielding, J. Gettys, J. Mogul, H. Frystyk, and T. Bernes-Lee, "Hypertext transfer protocol -- HTTP/1.1," Internet Request for Comments RFC

No context found.

R. Fielding , J. Gettys, J. Mogul, H. Frystyk and T. Berners-Lee, "Hypertext Transfer Protocol - - HTTP/1.1", Network Working Group, Request for Comments:

No context found.

Fielding R. T, et al., "Hypertext Transfer Protocol -- HTTP/1.1", Internet draft, IETF, 1996.

No context found.

R. Fielding et al., "Hypertext Transfer Protocol---HTTP/1.1," IETF RFC 2616, June 1999; available online at http:// www.ietf.org/rfc/rfc2616.txt.

No context found.

Fielding, R., Gettys, J., Mogul, J. C., Frystyk, H., Masinter, L., Leach, P., BernersLee, T., "Hypertext Transfer Protocol -- HTTP/1.1," IETF Proposed Standard, RFC 2068. http://www.w3c.org/Protocols/rfc2068/rfc2068

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC