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

[Drew Hess]

Peter Bex <address@hidden> 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 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'm looking forward to testing your "intarweb" egg, but I'll
probably wait until Chicken 4 is released.

thanks again
d

p.s. In my local version of the http egg, I replaced the definition
of http:read-request-attributes with the slightly-modified
rfc822-header->list procedure that I described in my previous email,
and it's working fine, too.

pgpNxZzKVw4Sn.pgp
Description: PGP signature