Interface CoreProtocolPNames
- All Known Subinterfaces:
AllClientPNames
- All Known Implementing Classes:
HttpProtocolParams
public interface CoreProtocolPNames
- Since:
- 4.0
- Version:
- $Revision: 576077 $
-
Field Summary
Fields Modifier and Type Field Description static StringHTTP_CONTENT_CHARSETDefines the charset to be used per default for encoding content body.static StringHTTP_ELEMENT_CHARSETDefines the charset to be used for encoding HTTP protocol elements.static StringORIGIN_SERVERDefines the content of the Server header.static StringPROTOCOL_VERSIONDefines theprotocol versionused per default.static StringSTRICT_TRANSFER_ENCODINGDefines whether responses with an invalid Transfer-Encoding header should be rejected.static StringUSE_EXPECT_CONTINUEActivates 'Expect: 100-continue' handshake for the entity enclosing methods.static StringUSER_AGENTDefines the content of the User-Agent header.static StringWAIT_FOR_CONTINUEDefines the maximum period of time in milliseconds the client should spend waiting for a 100-continue response.
-
Field Details
-
PROTOCOL_VERSION
Defines theprotocol versionused per default.This parameter expects a value of type
ProtocolVersion.- See Also:
- Constant Field Values
-
HTTP_ELEMENT_CHARSET
Defines the charset to be used for encoding HTTP protocol elements.This parameter expects a value of type
String.- See Also:
- Constant Field Values
-
HTTP_CONTENT_CHARSET
Defines the charset to be used per default for encoding content body.This parameter expects a value of type
String.- See Also:
- Constant Field Values
-
USER_AGENT
Defines the content of the User-Agent header.This parameter expects a value of type
String.- See Also:
- Constant Field Values
-
ORIGIN_SERVER
Defines the content of the Server header.This parameter expects a value of type
String.- See Also:
- Constant Field Values
-
STRICT_TRANSFER_ENCODING
Defines whether responses with an invalid Transfer-Encoding header should be rejected.This parameter expects a value of type
Boolean.- See Also:
- Constant Field Values
-
USE_EXPECT_CONTINUE
Activates 'Expect: 100-continue' handshake for the entity enclosing methods. The purpose of the 'Expect: 100-continue' handshake 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 noticable peformance 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:
- Constant Field Values
-
WAIT_FOR_CONTINUE
Defines the maximum period of time in milliseconds the client should spend waiting for a 100-continue response.
This parameter expects a value of typeInteger.- See Also:
- Constant Field Values
-