W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 2001

Re: doubt regarding http 1.1

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 17 Jul 2001 08:01:38 -0700
To: Joris Dobbelsteen <joris.dobbelsteen@mail.com>
Cc: "WWW WG (E-mail)" <http-wg@cuckoo.hpl.hp.com>
Message-ID: <20010717080132.E1211@mnot.net>

Yes, they're extensions, but all widely-used 1.0 implementations use
them, to the best of my knowledge. More to the point, many "1.1"
server implementations won't chunk some content, depending on how the
entity is generated, leading them to close the connection.
Conversely, if the generation engine supplies them with a
Content-Length header, they not only will not close the connection,
they won't chunk it, giving the desired effect.




On Tue, Jul 17, 2001 at 04:18:39PM +0200, Joris Dobbelsteen wrote:
> >-----Original Message-----
> >From: Mark Nottingham [mailto:mnot@mnot.net]
> >Sent: Monday, 02 July 2001 8:34
> >To: Joris Dobbelsteen
> >Cc: WWW WG (E-mail)
> >Subject: Re: doubt regarding http 1.1
> >
> >
> >
> >I'd echo Joris' question as to why in the world you'd want to disable
> >chunking, but...
> >
> ><shamless_plug>
> >http://www.mnot.net/cgi_buffer/
> >
> >Buffers Perl, Python and PHP scripts; also can act as a wrapper for
> >arbitrary code. Intended to be useful for 1.0 content, and for
> 
> HTTP/1.0 doesn't support chunking, nor persistent connections (yes, there
> are some extensions, but the origional spec doesn't support it). This way,
> ending a response is done by closing the connection.
> 
> >servers that don't chunk generated objects (most don't), but it
> >should be helpful here.
> ></shameless_plug>
> >
> >I think there are also Apache modules, etc. that may do this, look
> >at http://modules.apache.org/
> >
> >
> >
> >On Mon, Jul 02, 2001 at 01:16:46PM +0200, Joris Dobbelsteen wrote:
> >> Why not use it? It provided a way to keep the connection open.
> >>
> >> You can try Tranfer-Encoding: identify
> >> see RFC2616 par. 14.41
> >>
> >> There is also something with TE (par. 14.39).
> >>
> >> Note that Apache will need to cache the response before
> >transmitting it, to
> >> demitrade the length. I don't know wether they do or support
> >that (probably
> >> they do). It requires only an enormous ammount of overhead
> >on the server,
> >> not caused with chunked transfers. So why not use these,
> >it's simple to
> >> build some support for that.
> >>
> >> Before to forget, RFC2616 lists enough information in the
> >sections with
> >> tranfer-codings and such....
> >>
> >>
> >> Have fun...
> >>
> >> - Joris
> >>
> >> >-----Original Message-----
> >> >From: manish kumar [mailto:manishksinghal@hotmail.com]
> >> >Sent: Monday, 02 July 2001 12:12
> >> >To: http-wg@cuckoo.hpl.hp.com
> >> >Subject: doubt regarding http 1.1
> >> >
> >> >
> >> >Hi
> >> >I am using http 1.1.I am making a persistent connection from
> >> >java client to
> >> >apache server.I am able to make it but I don't want to use
> >> >transfer encoding
> >> >as chunked(which is there by default).Is there any way I can
> >> >do it.Where I
> >> >need to change it.If you need some more detail please let me know.
> >> >
> >> >-Manish
> >> >_______________________________________________________________
> >> >__________
> >> >Get Your Private, Free E-mail from MSN Hotmail at
> >> http://www.hotmail.com.
> >>
> >>
> >
> >--
> >Mark Nottingham
> >http://www.mnot.net/
> >
> >
> 

-- 
Mark Nottingham
http://www.mnot.net/
Received on Tuesday, 17 July 2001 16:04:54 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:43 EDT