Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 87150 invoked from network); 26 Sep 2002 11:50:17 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Sep 2002 11:50:17 -0000 Received: (qmail 3283 invoked by uid 97); 26 Sep 2002 11:50:54 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 3223 invoked by uid 97); 26 Sep 2002 11:50:53 -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 3191 invoked by uid 98); 26 Sep 2002 11:50:52 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Sender: jsdever Message-ID: <3D92F443.C6D6DF28@sympatico.ca> Date: Thu, 26 Sep 2002 07:49:23 -0400 From: Jeff Dever X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18 i586) X-Accept-Language: en 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> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Also from RFC2616: TEXT = CTL = quoted-string = ( <"> *(qdtext | quoted-pair ) <"> ) qdtext = > quoted-pair = "\" CHAR So \n and \r are in the range of CTL and are therefore not valid in the chunk-extension. Ortwin Gl�ck wrote: > Ryan Hoegg wrote: > > chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] ) > > chunk-ext-name = token > > chunk-ext-val = token | quoted-string > > token = 1* > > > > Since chunk-extension includes only tokens and an "=" I read this to say > > that neither \r or \n is allowed before the first CRLF in a chunk. > > But the quoted string may contain virtually ANY character, no? > > Legal: > 89ab;value\r\n > 89ab;key=value\r\n > 89ab;key=\"value\"\r\n > 89ab;key=\"line1\r\nline2\rline3\nline4\"\r\n > > Illegal: > 89ab;key=line1\rline2\r\n > 89ab;key=line1\r\nline2\r\n > > Since we ignore everything after the ; anyway, I don't want to parse > this, really. But we run into serious problems in the case where a \r\n > occurs within the quoted string! > I have never encountered a server using this in the real-world (but I > haven't seen enough servers). So once again: Has anybody ever see a > server using this? -- To unsubscribe, e-mail: For additional commands, e-mail: