PHWinfo - Afficher un message

28/03/2006, 22h29

In article <1143577214.964565.283830@g10g2000cwb.googlegroups .com>, "Prashant" <vprashant@gmail.com> writes:
> The HTTP 1.1 specification says that any HTTP 1.1 application must be
> capable of handing chunked responses. It is not quite clear if the
> server is expected to understand chunked messages (request).

Yes, any conforming HTTP/1.1 implementation MUST support the chunked
transfer-coding. RFC 2616 3.6.1. Note that servers are applications
in 2616 (1.3).

> Is there a
> reason why a client would send a chunked request?

Certainly - all the same reasons that a server might send a chunked
response. If the length of the content-body is unknown when the
request begins, for example, chunking relieves the client from having
to buffer it in its entirety just to determine the length.

In fact, chunking is arguably *more* useful for the client, since
HTTP ignores the availability of TCP half-close, so the client has
one fewer option than the server for indicating the end of its
message.

> And does a HTTP 1.1
> compatible server HAVE to implement chunked transfers?

It has to be able to receive and process them. An origin server
never has to chunk a response. A proxy or gateway may need to pass
a chunked response through.

--
Michael Wojcik michael.wojcik@microfocus.com

The surface of the word "profession" is hard and rough, the inside mixed with
poison. It's this that prevents me crossing over. And what is there on the
other side? Only what people longingly refer to as "the other side".
-- Tawada Yoko (trans. Margaret Mitsutani)

28/03/2006, 22h29	#2
Michael Wojcik Messages: n/a Hébergeur:	Re: HTTP chunked transfer In article <1143577214.964565.283830@g10g2000cwb.googlegroups .com>, "Prashant" <vprashant@gmail.com> writes: > The HTTP 1.1 specification says that any HTTP 1.1 application must be > capable of handing chunked responses. It is not quite clear if the > server is expected to understand chunked messages (request). Yes, any conforming HTTP/1.1 implementation MUST support the chunked transfer-coding. RFC 2616 3.6.1. Note that servers are applications in 2616 (1.3). > Is there a > reason why a client would send a chunked request? Certainly - all the same reasons that a server might send a chunked response. If the length of the content-body is unknown when the request begins, for example, chunking relieves the client from having to buffer it in its entirety just to determine the length. In fact, chunking is arguably more useful for the client, since HTTP ignores the availability of TCP half-close, so the client has one fewer option than the server for indicating the end of its message. > And does a HTTP 1.1 > compatible server HAVE to implement chunked transfers? It has to be able to receive and process them. An origin server never has to chunk a response. A proxy or gateway may need to pass a chunked response through. -- Michael Wojcik michael.wojcik@microfocus.com The surface of the word "profession" is hard and rough, the inside mixed with poison. It's this that prevents me crossing over. And what is there on the other side? Only what people longingly refer to as "the other side". -- Tawada Yoko (trans. Margaret Mitsutani)