Requests
330
Netscape Enterprise Server NSAPI Programmer’s Guide • April 2002 (Draft)
For more information on the criteria for being conditionally compliant, see the
Hypertext Transfer Protocol—HTTP/1.1 specification (RFC 2068) at:
http://www.ietf.org/rfc/rfc2068.txt?number=2068
Requests
A request from a browser to a server includes the following information:
•
Request Method, URI, and Protocol Version
•
Request Headers
•
Request Data
Request Method, URI, and Protocol Version
A browser can request information using a number of methods. The commonly
used methods include the following:
•
GET
—Requests the specified resource (such as a document or image)
•
HEAD
—Requests only the header information for the document
•
POST
—Requests that the server accept some data from the browser, such as
form input for a CGI program
•
PUT
—Replaces the contents of a server’s document with data from the browser
Request Headers
The browser can send headers to the server. Most are optional. Some commonly
used request headers are shown in Table E-1.
Table E-1
Common request headers
Request header
Description
Accept
The file types the browser can accept.
Authorization
Used if the browser wants to authenticate itself with a
server; information such as the username and password are
included.
Summary of Contents for ENTERPRISE SERVER 6.1
Page 1: ...NSAPI Programmer s Guide Netscape Enterprise Server Version6 1 April 2002 Draft...
Page 290: ...Miscellaneous 290 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...
Page 318: ...cinfo 318 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...
Page 336: ...Buffered Streams 336 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...
Page 344: ...344 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...
Page 350: ...350 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...
Page 356: ...356 Netscape Enterprise Server NSAPI Programmer s Guide April 2002 Draft...