|
|
|
The web server response will contain date, server, status, and content-type headers, plus some variable number of other headers as appropriate to the request and HTTP version specified in the request.
Response headers defining the properties of the output, such as Content-Encoding, will be included only when the header’s content is different from the default for that parameter--if the content is compressed, for example.
If your request did not include the Authorization header, or if the user ID or password is not valid, the server will return a WWW-Authenticate header.
If you have specified an incorrect enable password, or no enable password when one is required, the server will return a Avaya-implemented Enable-Authenticate header.
HTTP 1.1 uses a process called chunked encoding to deliver content to a client. The content body is transmitted in pieces, or chunks, with HTTP-generated markers (chunk delimiters) interspersed with the content text. See RFC 2616 for details.
You can avoid chunked encoding by specifying HTTP/1.0 in your POST method call; you can still use HTTP 1.l request headers, but the response will not be chunked.
|
|
|