Re: [Chicken-users] http egg can't parse valid HTTP headers

2009-02-06 Thread Drew Hess
Peter Bex peter@xs4all.nl writes: For the time being, I changed the HTTP egg's regex to remove the nonspace character match at the start of the submatch group, so Foo: and Foo: are allowed header values. Please give the new trunk a shot, and let me know whether it works for you. Hi

Re: [Chicken-users] http egg can't parse valid HTTP headers

2009-02-06 Thread Peter Bex
On Thu, Feb 05, 2009 at 04:28:59PM -0800, Drew Hess wrote: Hi Peter, Yes, that fix works for the particular case I was having a problem with. Thanks for updating the egg. Any idea when it'll be released? I just released it. It should appear in the egg repository shortly. Thanks for

Re: [Chicken-users] http egg can't parse valid HTTP headers

2009-02-05 Thread Mario Domenech Goulart
Hi Drew On Wed, 04 Feb 2009 23:27:24 -0800 Drew Hess dh...@bothan.net wrote: Changing the definition of the nested accum procedure from this: (define (rfc822-header-list iport #!key strict? (reader (cut read-line ))) (define (accum name bodies r) (cons (list name

Re: [Chicken-users] http egg can't parse valid HTTP headers

2009-02-05 Thread Peter Bex
On Wed, Feb 04, 2009 at 11:27:24PM -0800, Drew Hess wrote: Hi, The regex used to parse HTTP headers in http:read-request-attributes in the http egg isn't quite right. (let ((rx (if (feature? 'pregexp) ([\\-A-Za-z0-9]+):[ ]*([^ ].*) ([-A-Za-z0-9]+):[ ]*([^