Transparently coalesces chunks of a HTTP stream that uses Transfer-Encoding chunked.
Note that this class NEVER closes the underlying stream, even when close gets called. Instead, it will read until the "end" of its chunking on close, which allows for the seamless invocation of subsequent HTTP 1.1 calls, while not requiring the client to remember to read the entire contents of the response.
@author Ortwin Glueck @author Sean C. Sullivan @author Martin Elwin @author Eric Johnson @author Mike Bowler @author Michael Becke @author Oleg Kalnichevski @since 2.0This class lets a Servlet read its request data as an HTTP/1.1 chunked stream. Chunked streams are a way to send arbitrary-length data without having to know beforehand how much you're going to send. They are introduced by a "Transfer-Encoding: chunked" header, so if such a header appears in an HTTP request you should use this class to read any data.
Sample usage:
InputStream in = req.getInputStream(); if ( "chunked".equals( req.getHeader( "Transfer-Encoding" ) ) ) in = new ChunkedInputStream( in );
Because it would be impolite to make the authors of every Servlet include the above code, this is general done at the server level so that it happens automatically. Servlet authors will generally not create ChunkedInputStreams. This is in contrast with ChunkedOutputStream, which Servlets have to call themselves if they want to use it.
Fetch the software.
Fetch the entire Acme package.
@author Jef Poskanzer
@author Daniel Matuschek
@version $Id: ChunkedInputStream.java,v 1.6 2002/05/31 14:45:56 matuschd Exp $
Transparently coalesces chunks of a HTTP stream that uses Transfer-Encoding chunked.
Note that this class NEVER closes the underlying stream, even when close gets called. Instead, it will read until the "end" of its chunking on close, which allows for the seamless invocation of subsequent HTTP 1.1 calls, while not requiring the client to remember to read the entire contents of the response.
@author Ortwin Gl�ck @author Sean C. Sullivan @author Martin Elwin @author Eric Johnson @author Mike Bowler @author Michael Becke @author Oleg Kalnichevski @since 2.0Note that this class NEVER closes the underlying stream, even when close gets called. Instead, it will read until the "end" of its chunking on close, which allows for the seamless execution of subsequent HTTP 1.1 requests, while not requiring the client to remember to read the entire contents of the response.
@author Ortwin Glueck @author Sean C. Sullivan @author Martin Elwin @author Eric Johnson @author Mike Bowler @author Michael Becke @author Oleg Kalnichevski @since 4.0The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size indicator, followed by an OPTIONAL trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information necessary for the recipient to verify that it has received the full message.
Chunked-Body = *chunk last-chunk trailer CRLF chunk = chunk-size [ chunk-extension ] CRLF chunk-data CRLF chunk-size = 1*HEX last-chunk = 1*("0") [ chunk-extension ] CRLF chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] ) chunk-ext-name = token chunk-ext-val = token | quoted-string chunk-data = chunk-size(OCTET) trailer = *(entity-header CRLF) The chunk-size field is a string of hex digits indicating the size of the chunk. The chunked encoding is ended by any chunk whose size is zero, followed by the trailer, which is terminated by an empty line.
The trailer allows the sender to include additional HTTP header fields at the end of the message. The Trailer header field can be used to indicate which header fields are included in a trailer (see section 14.40).
A server using chunked transfer-coding in a response MUST NOT use the trailer for any header fields unless at least one of the following is true:
a)the request included a TE header field that indicates "trailers" is acceptable in the transfer-coding of the response, as described in section 14.39; or,
b)the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
This requirement prevents an interoperability failure when the message is being received by an HTTP/1.1 (or later) proxy and forwarded to an HTTP/1.0 recipient. It avoids a situation where compliance with the protocol would have necessitated a possibly infinite buffer on the proxy.
Note that this class NEVER closes the underlying stream, even when close gets called. Instead, it will read until the "end" of its chunking on close, which allows for the seamless invocation of subsequent HTTP 1.1 calls, while not requiring the client to remember to read the entire contents of the response.
@author Ortwin Glueck @author Sean C. Sullivan @author Martin Elwin @author Eric Johnson @author Mike Bowler @author Michael Becke @author Oleg Kalnichevski @since 2.0 | |
| |
| |
| |
| |
| |
| |
| |
| |
| |