Netscape ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manual page 21

Nsapi
Table of Contents

Advertisement

The example request shown below would be sent by a Netscape browser to request
the server
to send back the resource in
foo.com
body data is sent because the method is GET (the point of the request is to get some
data, not to send it.)
GET /index.html HTTP/1.0
User-agent: Mozilla
Accept: text/html, text/plain, image/jpeg, image/gif, */*
Host: example.com
The server receives the request and processes it. It handles each request
individually, although it may process many requests simultaneously. Each request
is broken down into a series of steps that together make up the request handling
process.
The server generates a response which includes the HTTP protocol version, HTTP
status code, and a reason phrase separated by spaces. This is normally followed by
a number of headers. The end of the headers is indicated by a blank line. The body
data of the response follows. A typical HTTP response might look like this:
HTTP/1.0 200 OK
Server: Netscape-Enterprise/6.0
Content-type: text/html
Content-length: 83
<HTML>
<HEAD><TITLE>Hello World</Title></HEAD>
<BODY>Hello World</BODY>
</HTML>
The status code and reason phrase tell the client how the server handled the
request. Normally the status code 200 is returned indicating that the request was
handled successfully and the body data contains the requested item. Other result
codes indicate redirection to another server or the browser's cache, or various types
of HTTP errors such as "404 Not Found."
How the Server Handles Requests from Clients
. In this example, no
/index.html
Chapter 1
Basics of Server Operation
21

Advertisement

Table of Contents
loading

This manual is also suitable for:

Enterprise server 6.0

Table of Contents