T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," Request for Comments 1738, Internet Engineering Task Force, Dec. 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....behavior of a stateful proxy is further defined in Section 17.3. A stateful proxy is not the same as a call stateful proxy. Upstream: Responses sent in the direction from the user agent server to the user agent client. URL encoded: A character string encoded according to RFC 1738, Section 2. 2 [10]. User agent client (UAC) A user agent client is a logical entity that initiates a SIP transaction with a request. This role lasts only for the duration of that transaction. In other words, if a piece of software initiates a request, it acts as a UAC for the duration of that request. If it ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," Request for Comments 1738, Internet Engineering Task Force, Dec. 1994.

....port of host, and the Request URI for the resource is rtsp URL. The use of IP addresses in URLs SHOULD be avoided whenever possible (see RFC 1924 [19] A presentation or a stream is identified by a textual media identifier, using the character set and escape conventions [H3.2] of URLs (RFC 1738 [20]) URLs may refer to a stream or an aggregate of streams, i.e. a presentation. Accordingly, requests described in Section 10 can apply to either the whole presentation or an individual stream within the presentation. Note that some request methods can only be applied to streams, not presentations ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," RFC 1738, Internet Engineering Task Force, Dec. 1994.

....at least for the duration of a SIP transaction. The behavior of a stateful proxy is further defined in Section 12.3. Upstream: Responses sent in the direction from the user agent server to the user agent client. URL encoded: A character string encoded according to RFC 1738, Section 2. 2 [10]. User agent client (UAC) A user agent client is a client application that initiates a SIP request. User agent server (UAS) A user agent server is a server application that contacts the user when a SIP request is received and that returns a response on behalf of the user. The response accepts, ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," Request for Comments 1738, Internet Engineering Task Force, Dec. 1994.

....the UAC core, UAS core, and proxy core. 651 Upstream: A direction of message forwarding within a transaction which refers to the direction that re 652 sponses flow from the user agent server to user agent client. 653 URL encoded: A character string encoded according to RFC 1738, Section 2. 2 [10]. 654 User agent client (UAC) A user agent client is a logical entity that creates a new request, and then uses 655 the client transaction state machinery to send it. The role of UAC lasts only for the duration of that 656 transaction. In other words, if a piece of software initiates a request, ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," Request for Com- 5127 ments 1738, Internet Engineering Task Force, Dec. 1994. 5128

....the only reason it scales is, because the DNS name to address bindings hardly change. This cannot be assumed in general. For example, the World Wide Web suffers from a lack of location transparency. WWW names (URLs) depend on DNS domain names and usually on a filename on the server s file systems [1] . Thus, URLs are coupled to hosts. If one WWW document, such as a user s home page, has to move to another WWW server or to another directory it has to get a new URL. Even worse is replication transparency in today s systems. There are mirrors for heavily used WWW and ftp sites, but the same ....

T. Berners-Lee, L. Masinter, and M. McCahill. "Uniform Resource Locators (URL)". RFC 1738, December 1994.

....any valid HTTP 1.1 request from an ordinary Web client without WebDAV extensions, and to provide a valid HTTP 1.1 response that does not require the client to understand the extensions. 4.4. Data Format Compatibility WebDAV compliant servers should be able to work with existing resources and URIs [URL] Special additional information should not become a mandatory part of document formats. 4.5. Replicated, Distributed Systems Distribution and replication are at the heart of the Internet. All WebDAV extensions should be designed to allow for distribution and replication. Version trees should be ....

....5.8.1.2. Make Collection. It must be possible to create a new collection. 5.8.1.3. Add to Collection. It must be possible to add a resource to a collection directly or by reference. 5.8.1.4. Remove from Collection. It must be possible to remove a resource from a collection. 5.8.2. Rationale In [URL] it states that, some URL schemes (such as the ftp, http, and file schemes) contain names that can be considered hierarchical. Especially for HTTP servers which directly map all or part of their URL name space into a filesystem, it is very useful to get a listing of all resources located at a ....

[Article contains additional citation context not shown here]

Berners-Lee, T., Masinter, L., and M. McCahill. "Uniform Resource Locators (URL)", RFC 1738, December 1994.

....The interfaces between the Web and object or objectrelational databases can also be classified 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 ....

Berners-Lee T, Masinter L and McCahill M: `Uniform Resource Locators (URL)', RFC 1738, CERN, Xerox PARC, University of Minnesota (December 1994), http://ds.internic.net/rfc/rfc1738.txt

....on that port of host, and the Request URI for the resource is rtsp URL. The use of IP addresses in URLs SHOULD be avoided whenever possible (see RFC 1924 [15] A presentation or a stream is identified by a textual media identifier, using the character set and escape conventions [H3.2] of URLs [17]. URLs may refer to a stream or an aggregate of streams, i.e. a presentation. Accordingly, requests described in Section 10 can apply to either the whole presentation or an individual stream within the presentation. Note that some request methods can only be applied to streams, not presentations ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," RFC 1738, Internet Engineering Task Force, Dec. 1994.

....on that port of host, and the Request URI for the resource is rtsp URL. The use of IP addresses in URLs SHOULD be avoided whenever possible (see RFC 1924 [15] A presentation or a stream is identified by an textual media identifier, using the character set and escape conventions [H3.2] of URLs [17]. URLs may refer to a stream or an aggregate of streams i.e. a presentation. Accordingly, requests described in Section 10 can apply to either the whole presentation or an individual stream within the presentation. Note that some request methods can only be applied to streams, not presentations and ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," RFC 1738, Internet Engineering Task Force, Dec. 1994.

....leg. The ACK request has the same CSeq number as the corresponding INVITE request, but comprises a transaction of its own. Upstream: Responses sent in the direction from the user agent server to the user agent client. URL encoded: A character string encoded according to RFC 1738, Section 2. 2 [13]. User agent client (UAC) A user agent client is a client application that initiates a SIP request. Handley Schulzrinne Schooler Rosenberg Expires January 2000 [Page 10] INTERNET DRAFT draft ietf sip rfc2543bis 02.ps September 4, 2000 User agent server (UAS) A user agent server is a server ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," Request for Comments 1738, Internet Engineering Task Force, Dec. 1994.

....downloaded as part of the resource. PICS also specifies protocols for a web site to provide a special server for providing ratings of its web pages, and protocols for services which provide ratings also for other web pages than its own. The resource being rated is identified by its URL. Since URLs [12] are not only available for web pages, but also for e mail messages, Usenet News newsgroups and messages, etc. PICS can be used to rate all resources for which URLs are defined. Some Problems with Rating Some problems which can cause rating to work less well are: 1. Too few ratings are provided ....

T. Berners-Lee, L. Masinter, M. McCahill, "Uniform Resource Locators (URL)", by T. Berners-Lee, L. Masinter, M. McCahill , Internet RFC 1738, December 1994. This is the Internet standard for URLs. There are numerous other IETF standards specifying the URL format for different kinds of resources.

....on that port of host, and the Request URI for the resource is rtsp URL. The use of IP addresses in URLs SHOULD be avoided whenever possible (see RFC 1924 [15] A presentation or a stream is identified by a textual media identifier, using the character set and escape conventions [H3.2] of URLs [16]. URLs may refer to a stream or an aggregate of streams, i.e. a presentation. Accordingly, requests described in Section 10 can apply to either the whole presentation or an individual stream within the presentation. Note that some request methods can only be applied to streams, not presentations ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (URL)," RFC 1738, Internet Engineering Task Force, Dec. 1994.

....clientserver, con supporto di rete [5] affidato al protocollo di comunicazione TCP IP. In poche parole, i server di informazione (siti di rete) custodiscono i documenti Web e li consegnano su richiesta ai client (tipicamente i browser Web) Seguendo i link ipertestuali (Uniform Resource Locators) [4] all interno di un documento si rende possibile, in maniera del tutto trasparente, la cosiddetta navigazione virtuale di sito in sito. Nonstante l enorme e continuo sviluppo (sull onda anche della crescente popolarit a) della tecnologia sottostante al Web, non e stata finora prestata la dovuta ....

T. Berners-Lee, L. Masinter, M. McCahill, "Uniform Resource Locators (URL)," RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

....employ a hierarchical naming scheme that corresponds to the hierarchical organization of the entities of interest. The state ofthe art in Internet scale structure based naming models is the Universal Resource Locator (URL) which provides a way of locating and accessing Internet resources [3]. URLs could be used as the realization for a facility s naming model, but the URL syntax and semantics would have to be extended to support the naming of additional kinds of objects; work in this direction is the subject of a draft specification for Uniform Resource Identifiers (URIs) 8] In a ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform Resource Locators (URL)", Internet Engineering Task Force, Request for Comments RFC 1738, December 1994.

....only reason it scales is, because the DNS name to address bindings hardly change. This cannot be assumed in general. For example, the World Wide Web suffers from a lack of location transparency. WWW names (URLs) depend on DNS domain names and usually on a filename on the server s file systems [1]. Thus, URLs are coupled to hosts. If one WWW document, such as a user s home 1. Author s current address is IMMD IV, University Erlangen N rnberg, Germany. Franz J. Hauck, Maarten van Steen, Andrew S. Tanenbaum 2 page, has to move to another WWW server or to another directory it has to get a ....

T. Berners-Lee, L. Masinter, M. McCahill. "Uniform Resource Locators (URL)." RFC 1738, Dec. 1994.

....unique; it may be the same as that chosen by the conference initiator. 2 The conference name is arbitrary, case sensitive, can be of any length, and may contain letters, digits, and punctuation characters except the slash. Slashes were chosen as a hierarchy indicator to align with URL usage [16] and since they are not used within domain names. An URL like escape mechanism permits the use of other characters. A typical conference name would be the name advertised by the session directory tool sd. The media agent responds: M C: 17 audio 3 created The controller then proceeds to ....

T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource locators (url)," Internet Draft, URI Working Group, Sept. 1994. Work in progress.

....as http URLs in which the server name references a Handle Proxy Server. For example, a Handle Proxy URL http: hdl.handle.net jis cnri.test will submit the HandleRef jis cnri.test to the proxy service hdl.handle.net . Note that the URL contains illegal characters according to RFC1738 [21], but never the less works. Handles specified using Handle Proxy URL syntax are subject to the syntax restrictions on http URLs, specifically the set of reserved excluded characters as defined in RFC1738 [21] The proxy server performs the handle resolution task, and sends the resulting URL to ....

.... hdl.handle.net . Note that the URL contains illegal characters according to RFC1738 [21] but never the less works. Handles specified using Handle Proxy URL syntax are subject to the syntax restrictions on http URLs, specifically the set of reserved excluded characters as defined in RFC1738 [21]. The proxy server performs the handle resolution task, and sends the resulting URL to the client browser for processing. Currently, CNRI provides global handle proxy service through hdl.handle.net . Even though using the proxy server approach is straight forward and does not require any customer ....

Berners-Lee, T., Masinter, L., McCahill, M., et al., "Uniform Resource Locators (URL)", RFC1738, December 1994. http://ds.internic.net/rfc/rfc1738.txt

....objects in practice reveals that they can be summarized into three categories: the Limited Character Set Approach, the Use of Encoding Tags, and the Unicode Based Encoding. 2.2.1. The Limited Character Set Approach An example of this approach is the current URL specification defined in RFC1738[10] and RFC1808[11] The URL specification defines a subset of the US ASCII character set as the only legal characters for use in the URL context, and specifies that all other characters, including those of any non English languages, must be hex encoded (e.g. FF) when used in the URL. Restricting ....

.... http: ProxyServer HandleRef In this case, the Proxy Server is the domain name of a proxy server that will be responsible for resolving the Handle and directing the resolution results back to the client. Since this is a URL, any reserved excluded characters in the URL specifications [10, 11] will have to be hex encoded when used in the HandleRef . Examples of handles using Handle Proxy Syntax are: http: hdl.handle.net cnri.dlib july95 arms http: hdl.handle.net jis cnri.test http: hdl.handle.net cnri.test handle 25abc Here hdl.handle.net is a proxy service provided by CNRI to ....

Berners-Lee, T., Masinter, L., McCahill, M., et al., "Uniform Resource Locators (URL)" RFC1738, December 1994. http://ds.internic.net/rfc/rfc1738.txt

....( is sent similarly for individual transmitters. In addition to assigning addresses and keys for sending outof band data, the key manager provides a mechanism for sending small amounts of in band data. This is currently intended primarily as a means for sources to send a URL [2] for some sound, image or video sequence that they wish recipients to retrieve and display. Values can be sent to a device s broadcast set using the broadcast value( method, or to a specific channel using transmit value( Sinks The methods on the key manager called by sinks and the ....

Berners-Lee, T., L. Masinter, and M. McCahill, "Uniform Resource Locators (URL)," IETF Request for Comments RFC 1738, available from ftp://ftp.internic.net/rfc/rfc1738.txt.

....than simple retrieval, including search, front end update, and annotation. HTTP allows an open ended set of methods and headers that indicate the purpose of a request [47] It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) 3] as a location (URL) [4] or name (URN) 20] for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by Internet mail [9] as defined by the Multipurpose Internet Mail Extensions (MIME) 7] HTTP is also used as a generic protocol for communication between user ....

....modification of header fields required or forbidden by the versions involved. 3. 2 Uniform Resource Identifiers URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers [3] and finally the combination of Uniform Resource Locators (URL) [4] and Names (URN) 20] As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify via name, location, or any other characteristic a resource. 3.2.1 General Syntax URIs in HTTP can be represented in absolute form or relative to some known base URI ....

[Article contains additional citation context not shown here]

Berners-Lee, T., Masinter, L., and M. McCahill. "Uniform Resource Locators (URL)," RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

....more functionality than simple retrieval, including search, front end update, and annotation. HTTP allows an open ended set of methods that indicate the purpose of a request. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) 3] 20] as a location (URL) [4] or name (URN) for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by Internet mail as defined by theand the Multipurpose Internet Mail Extensions (MIME) HTTP is also used as a generic protocol for communication between user ....

....with a scheme name followed by a colon. HTTP Version = HTTP 1 DIGIT . 1 DIGIT INTERNET DRAFT Hypertext Transfer Protocol HTTP 1. 1 Monday, June 03, 1996 Fielding, Frystyk, Berners Lee, Gettys, and Mogul [Page 18] For definitive information on URL syntax and semantics, see RFC 1738 [4] and RFC 1808 [11] The BNF above includes national characters not allowed in valid URLs as specified by RFC 1738, since HTTP servers are not restricted in the set of unreserved characters allowed to represent the rel path part of addresses, and HTTP proxies may receive requests for URIs not ....

T. Berners-Lee, L. Masinter, M. McCahill. "Uniform Resource Locators (URL)." RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

....require more functionality than simple retrieval, including search, front end update, and annotation. HTTP allows an open ended set of methods that indicate the purpose of a request. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) 3] as a location (URL) [4] or name (URN) 20] for indicating the resource on which a method is to be applied. Messages are passed in a format similar to that used by Internet Mail [9] and the Multipurpose Internet Mail Extensions (MIME) 7] HTTP is also used as a generic protocol for communication between user agents and ....

....involved. It is likely more involved than just changing the version indicator. 3. 2 Uniform Resource Identifiers URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers [3] and finally the combination of Uniform Resource Locators (URL) [4] and Names (URN) 20] As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify via name, location, or any other characteristic a network resource. quoted pair = CHAR HTTP Version = HTTP 1 DIGIT . 1 DIGIT INTERNET DRAFT Hypertext ....

[Article contains additional citation context not shown here]

T. Berners-Lee, L. Masinter, M. McCahill. "Uniform Resource Locators (URL)." RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

....more functionality than simple retrieval, including search, front end update, and annotation. HTTP allows an open ended set of methods that indicate the purpose of a request. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) 3] 20] as a location (URL) [4] or name (URN) for indicating the resource to which a 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) HTTP is also used as a generic protocol for communication between user agents and ....

....be represented in absolute form or relative to some known base URI , depending upon the context of their use. The two forms are differentiated by the fact that absolute URIs always begin with a scheme name followed by a colon. For definitive information on URL syntax and semantics, see RFC 1738 [4] and RFC 1808 [11] The BNF above includes national characters not allowed in valid URLs as specified by RFC 1738, since HTTP servers are not restricted in the set of unreserved characters allowed to represent the rel path part of addresses, and HTTP proxies may receive requests for URIs not ....

T. Berners-Lee, L. Masinter, M. McCahill. "Uniform Resource Locators (URL)." RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

....require more functionality than simple retrieval, including search, front end update, and annotation. HTTP allows an open ended set of methods that indicate the purpose of a request. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) 3] as a location (URL) [4] or name (URN) 20] for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by Internet mail [9] as defined by the Multipurpose Internet Mail Extensions (MIME) 7] HTTP is also used as a generic protocol for communication between user ....

....INTERNET DRAFT HTTP 1.1 Wednesday, July 30, 1997 Fielding, et al. [Page 16] 3. 2 Uniform Resource Identifiers URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers [3] and finally the combination of Uniform Resource Locators (URL) [4] and Names (URN) 20] As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify via name, location, or any other characteristic a resource. 3.2.1 General Syntax URIs in HTTP can be represented in absolute form or relative to some known base URI ....

[Article contains additional citation context not shown here]

Berners-Lee, T., Masinter, L., and M. McCahill. "Uniform Resource Locators (URL)," RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994.

No context found.

Berners-Lee, T., Masinter, L., and M. McCahill, Editors. "Uniform Resource Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of Minnesota, December 1994.

First 50 documents

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