IETF Logo Mail Archive

Re: RE: IPP> Implementation question re.: chunking

"Carl Kugler" <kugler@us.ibm.com> Fri, 24 July 1998 19:16 UTC

Delivery-Date: Fri, 24 Jul 1998 15:16:37 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA24193 for <ietf-archive@ietf.org>; Fri, 24 Jul 1998 15:16:37 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA18977 for <ietf-archive@cnri.reston.va.us>; Fri, 24 Jul 1998 15:16:27 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id PAA05570 for <ietf-archive@cnri.reston.va.us>; Fri, 24 Jul 1998 15:16:36 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Fri, 24 Jul 1998 15:12:29 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id PAA04995 for ipp-outgoing; Fri, 24 Jul 1998 15:03:34 -0400 (EDT)
Date: Fri, 24 Jul 1998 19:02:39 -0000
Message-ID: <19980724190239.9548.qmail@m2.findmail.com>
From: Carl Kugler <kugler@us.ibm.com>
Subject: Re: RE: IPP> Implementation question re.: chunking
In-Reply-To: <CB6657D3A5E0D111A97700805FFE6587BF6F37@red-msg-51.dns.microsoft.com>
To: ipp@pwg.org
Sender: owner-ipp@pwg.org

Okay, as a practical matter it looks like we need to be able to support HTTP/1.0 in addition to HTTP/1.1, and "Content-Length" in addition to "Transfer-Encoding: chunked" whether sending or receiving.  

This leads me to my next question: What is the transition sequence for the cases in which an HTTP/1.1 client that normally uses chunking wants to make a request of a server that is HTTP/1.0 and/or doesn't understand chunking?  

Does this scenario look correct?:

1. Client requests HTTP/1.1, Transfer-Encoding: chunked 
2. Server responds HTTP/1.0 501 (Unimplemented), and closes the connection
3. Client opens new connection and requests HTTP/1.0, Content-Length

Also, don't some HTTP/1.0 implementations understand Transfer-Encoding as an extension?  We have some client situations where we can't avoid chunking, so it would be nice if even the HTTP/1.0 servers understood chunked transfer coding.  (Presumably all HTTP/1.1 applications are able to receive and decode the “chunked” transfer coding.)

    -Carl

>You might find that some implementations dont support chunking.
> 
> > -----Original Message-----
> > From:	Randy Turner [SMTP:rturner@sharplabs.com]
> > Sent:	Friday, July 24, 1998 10:05 AM
> > To:	Carl Kugler
> > Cc:	ipp@pwg.org
> > Subject:	Re: IPP> Implementation question re.:  chunking
> > 
> > At 04:51 PM 7/24/98 +0000, you wrote:
> > >draft-ietf-ipp-protocol-06.txt says the client and server MUST support
> > the
> > "chunked" transfer encoding when receiving.  My question is:  Can we count
> > on this?  I.e., if our client always transmits requests using the
> > "chunked"
> > transfer encoding, will we be able to interoperate with the vast majority
> > of IPP server implementations?
> > >
> > >    -Carl
> > 
> > 
> > There are no vast majority of IPP server implementations (yet). I think
> > the
> > only worry is if someone plans to deploy IPP behind a generic web server
> > that doesn't support chunking. However, Apache and most other of the more
> > popular HTTP/1.1 servers will support this. It should definitely be a
> > bullet item (checkoff item) at the upcoming bake-off, however.
> > 
> > Randy
> > 
> > > 
> 
> 



-----
Original Message: http://www.findmail.com/list/ipp/?start=4179
Start a FREE email list at http://www.FindMail.com/

v2.23.0 | Report a Bug | By Email