Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 3542 invoked from network); 26 Sep 2002 12:11:55 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Sep 2002 12:11:55 -0000 Received: (qmail 21413 invoked by uid 97); 26 Sep 2002 12:12:32 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 21363 invoked by uid 97); 26 Sep 2002 12:12:31 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 21341 invoked by uid 98); 26 Sep 2002 12:12:30 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D92FA0C.2000001@nose.ch> Date: Thu, 26 Sep 2002 14:14:04 +0200 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: de-ch, en-us MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [PATCH][HttpClient] bug 12607 References: <3D8F24A9.2010208@nose.ch> <3D9015A3.26C16C66@sympatico.ca> <3D901EE9.50908@nose.ch> <3D90A693.7080500@isisnetworks.net> <3D92BD6D.4030201@nose.ch> <3D92F7FF.2010903@isisnetworks.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N LWS = [CRLF] 1*( SP | HT ) Damn. We must parse this shit.... Ryan Hoegg wrote: > I have never seen a server do this, but you are right about the > quoted-string: > > quoted-string = ( <"> *(qdtext | quoted-pair ) <"> ) > quoted-pair = "\" CHAR > qdtext = > > > TEXT = but including LWS> > > So it seems that for each cunk-ext-val, we need to: > 1) read the first char > 2) if it is not a <">, proceed as we currently do > 3) if it is, continue to read chars until a <"> or a <\> is reached > 4) in the case of a <\>, skip the next character > 5) in the case of a <">, ensure that we either have CRLF or <;> > 6) if we have <;>, we read another i.e. goto 1 > > This is my reading of RFC2616. -- To unsubscribe, e-mail: For additional commands, e-mail: