Interface CoreProtocolPNames
- All Known Implementing Classes:
HttpProtocolParams
- Since:
- 4.0
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringDeprecated.Defines the charset to be used per default for encoding content body.static final StringDeprecated.Defines the charset to be used for encoding HTTP protocol elements.static final StringDeprecated.Defines the action to perform upon receiving a malformed input.static final StringDeprecated.Defines the action to perform upon receiving an unmappable input.static final StringDeprecated.Defines the content of theServerheader.static final StringDeprecated.Defines theProtocolVersionused per default.static final StringDeprecated.Defines whether responses with an invalidTransfer-Encodingheader should be rejected.static final StringDeprecated.Activates 'Expect: 100-Continue' handshake for the entity enclosing methods.static final StringDeprecated.Defines the content of theUser-Agentheader.static final StringDeprecated.Defines the maximum period of time in milliseconds the client should spend waiting for a 100-continue response.
-
Field Details
-
PROTOCOL_VERSION
Deprecated.Defines theProtocolVersionused per default.This parameter expects a value of type
ProtocolVersion.- See Also:
-
HTTP_ELEMENT_CHARSET
-
HTTP_CONTENT_CHARSET
-
USER_AGENT
-
ORIGIN_SERVER
-
STRICT_TRANSFER_ENCODING
-
USE_EXPECT_CONTINUE
Deprecated.Activates 'Expect: 100-Continue' handshake for the entity enclosing methods. The purpose of the 'Expect: 100-Continue' handshake is to allow a client that is sending a request message with a request body to determine if the origin server is willing to accept the request (based on the request headers) before the client sends the request body.
The use of the 'Expect: 100-continue' handshake can result in a noticeable performance improvement for entity enclosing requests (such as POST and PUT) that require the target server's authentication.
'Expect: 100-continue' handshake should be used with caution, as it may cause problems with HTTP servers and proxies that do not support HTTP/1.1 protocol.
This parameter expects a value of typeBoolean.- See Also:
-
WAIT_FOR_CONTINUE
-
HTTP_MALFORMED_INPUT_ACTION
Deprecated.Defines the action to perform upon receiving a malformed input. If the input byte sequence is not legal for this charset then the input is said to be malformed
This parameter expects a value of typeCodingErrorAction- Since:
- 4.2
- See Also:
-
HTTP_UNMAPPABLE_INPUT_ACTION
Deprecated.Defines the action to perform upon receiving an unmappable input. If the input byte sequence is legal but cannot be mapped to a valid Unicode character then the input is said to be unmappable
This parameter expects a value of typeCodingErrorAction- Since:
- 4.2
- See Also:
-