Connected: An Internet Encyclopedia
RFC 1738 - 3. Specific Schemes

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1738
Prev: 2.3 Hierarchical schemes and relative links
Next: 3.1. Common Internet Scheme Syntax

### 3. Specific Schemes

The mapping for some existing standard and experimental protocols is outlined in the BNF syntax definition. Notes on particular protocols follow. The schemes covered are:

       ftp                     File Transfer protocol
       http                    Hypertext Transfer Protocol
       gopher                  The Gopher protocol
       mailto                  Electronic mail address
       news                    USENET news
       nntp                    USENET news using NNTP access
       telnet                  Reference to interactive sessions
       wais                    Wide Area Information Servers
       file                    Host-specific file names
       prospero                Prospero Directory Service

Other schemes may be specified by future specifications. Section 4 of this document describes how new schemes may be registered, and lists some scheme names that are under development.

3.1. Common Internet Scheme Syntax
3.2. FTP

3.2.1. FTP Name and Password
3.2.2. FTP url-path
3.2.3. FTP Typecode is Optional
3.2.4 Hierarchy
3.2.5. Optimization

3.3. HTTP
3.4. GOPHER

3.4.1. Gopher URL syntax
3.4.2 Specifying URLs for Gopher Search Engines
3.4.3 URL syntax for Gopher+ items
3.4.4 Default Gopher+ data representation
3.4.5 Gopher+ items with electronic forms
3.4.6 Gopher+ item attribute collections
3.4.7 Referring to specific Gopher+ attributes
3.4.8 URL syntax for Gopher+ alternate views
3.4.9 URL syntax for Gopher+ electronic forms

3.5. MAILTO
3.6. NEWS
3.7. NNTP
3.8. TELNET
3.9. WAIS
3.10 FILES
3.11 PROSPERO

Next: 3.1. Common Internet Scheme Syntax

Connected: An Internet Encyclopedia
RFC 1738 - 3. Specific Schemes