Apache HttpClient 4.5.14 · org.apache.http.conn.params.ConnConnectionPNames

public Interface ConnConnectionPNames

Parameter names for HTTP client connections.

Since

4.0

Field Summary

Modifier and Type	Field and Description
public static final String	MAX_STATUS_LINE_GARBAGE Defines the maximum number of ignorable lines before we expect a HTTP response's status line.

Field Detail

MAX_STATUS_LINE_GARBAGE back to summary

MAX_STATUS_LINE_GARBAGE	back to summary
public static final String MAX_STATUS_LINE_GARBAGE Deprecated (4.1) Use custom `org.apache.http.impl.conn.DefaultHttpResponseParser` implementation Defines the maximum number of ignorable lines before we expect a HTTP response's status line. With HTTP/1.1 persistent connections, the problem arises that broken scripts could return a wrong Content-Length (there are more bytes sent than specified). Unfortunately, in some cases, this cannot be detected after the bad response, but only before the next one. So HttpClient must be able to skip those surplus lines this way. This parameter expects a value of type `Integer`. 0 disallows all garbage/empty lines before the status line. Use `java.lang.Integer#MAX_VALUE` for unlimited number. Annotations @Deprecated

public static final String MAX_STATUS_LINE_GARBAGE

Deprecated

(4.1) Use custom org.apache.http.impl.conn.DefaultHttpResponseParser implementation

Defines the maximum number of ignorable lines before we expect a HTTP response's status line.

With HTTP/1.1 persistent connections, the problem arises that broken scripts could return a wrong Content-Length (there are more bytes sent than specified). Unfortunately, in some cases, this cannot be detected after the bad response, but only before the next one. So HttpClient must be able to skip those surplus lines this way.

This parameter expects a value of type Integer. 0 disallows all garbage/empty lines before the status line. Use java.lang.Integer#MAX_VALUE for unlimited number.

Annotations

@Deprecated