HTTP (pdk.net.http)

Contains structures that provide support for HTTP calls

Represents an HTTP cookie, which carries state information between server and user agent. Cookie is widely adopted to create stateful sessions.

There are 3 HTTP cookie specifications:

Netscape draft RFC 2109 - RFC 2965 -

HttpCookie class can accept all these 3 forms of syntax.

Properties:

comment ::
domain ::
expiry ::
httpOnly ::
maxAge ::
name ::
path ::
secure ::
value ::
version ::

Superstructures: <-

Header

For example, if a response header instance contains one key "HeaderName" with two values "value1 and value2" then this object is output as two header lines:

 HeaderName: value1
 HeaderName: value2

Properties:

Request

Represents one HTTP request which can be sent to a server.

Properties:

data :: T

Response

A HttpResponse is available when the response status code and headers have been received, and typically after the response body has also been received. This depends on the response body handler provided when sending the request. In all cases, the response body handler is invoked before the body is read. This gives applications an opportunity to decide how to handle the body.

Methods are provided in this class for accessing the response headers, and response body.

Properties:

data :: T
errorData :: V

EmptyRequest

Represents empty data to be sent. (e.g. POST method with no payload)

EmptyResponse

Represents empty response data. (e.g. POST method that returns only status code)

FormData

Represents form data that is submitted via an HTTP POST request.

Properties:

FileFormDataEntry

Represents form data entry with file content.

Properties:

TextFormDataEntry

Represents form data entry with text content.

Properties:

PreviousNetworking (pdk.net)NextSOAP/Web Services (pdk.net.soap)

Last updated 5 months ago

Represents an HTTP cookie, which carries state information between server and user agent. Cookie is widely adopted to create stateful sessions.

There are 3 HTTP cookie specifications:

Netscape draft RFC 2109 - RFC 2965 -

HttpCookie class can accept all these 3 forms of syntax.

Properties:

comment ::
domain ::
expiry ::
httpOnly ::
maxAge ::
name ::
path ::
secure ::
value ::
version ::

Superstructures: <-

Header

HTTP request and response headers are represented by this structure. The name is case-insensitive representing the header name and the value associated with each name is an <> with one element for each occurrence of the header name in the request or response.

For example, if a response header instance contains one key "HeaderName" with two values "value1 and value2" then this object is output as two header lines:

 HeaderName: value1
 HeaderName: value2

Properties:

name ::
values :: <>

Superstructures: <-

Request

Represents one HTTP request which can be sent to a server.

Properties:

cookie :: <>
data :: T
header :: <>

Superstructures: <-

Response

Represents a response to a

A HttpResponse is available when the response status code and headers have been received, and typically after the response body has also been received. This depends on the response body handler provided when sending the request. In all cases, the response body handler is invoked before the body is read. This gives applications an opportunity to decide how to handle the body.

Methods are provided in this class for accessing the response headers, and response body.

Properties:

cookie :: <>
data :: T
errorData :: V
header :: <>
statusCode ::

Superstructures: <-

EmptyRequest

Represents empty data to be sent. (e.g. POST method with no payload)

Superstructures: <-

EmptyResponse

Represents empty response data. (e.g. POST method that returns only status code)

Superstructures: <-

FormData

Represents form data that is submitted via an HTTP POST request.

Properties:

files :: <>
parameters :: <>

Superstructures: <-

FileFormDataEntry

Represents form data entry with file content.

Properties:

name ::
value ::

Superstructures: <-

TextFormDataEntry

Represents form data entry with text content.

Properties:

name ::
value ::

Superstructures: <-

HTTP request and response headers are represented by this structure. The name is case-insensitive representing the header name and the value associated with each name is an <> with one element for each occurrence of the header name in the request or response.

name ::

values :: <>

Superstructures: <-

cookie :: <>

header :: <>

Superstructures: <-

Represents a response to a

cookie :: <>

header :: <>

statusCode ::

Superstructures: <-

files :: <>