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 repor
Peter Bex 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, t
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]+)
Hi Drew
On Wed, 04 Feb 2009 23:27:24 -0800 Drew Hess 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 (string-concatenate-reverse
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]+):[ ]*([^ ].*)") ) )
RFC 2616 states in Section 4.2 that HTTP headers "
