Re: header parsing

[Andy Wingo]

Hi Ian,

On Fri 09 Sep 2011 11:42, Ian Price <address@hidden> writes:

> Writing a quick script the other day I came across two issues when
> guile parses http headers. The first is that 'parse-rfc-822-date' does
> not allow for single digit days, which are allowed in rfc822/1123 [0].

Applied, thanks.

> Secondly, a non-guile problem, is that many sites don't quote their
> etags. While I can (and did) account for this myself with
> 'declare-header!', I was wondering if it would be better to modify
> 'parse-qstring' to fallback to 'parse-opaque-string' if the start isn't
> a #\" character. This would be in line with Postel's law[1], but the
> commentary at the top of http.scm says there shouldn't be too many
> compatibility hacks.

I'm a bit hesitant on this one, as parse-qstring is used in so many
other places.  Perhaps change this one to add parse-opaque-or-qstring or
something, and call that from parse-etag?  Dunno.  Are there really many
sites that do this to their etags?

Cheers,

Andy
-- 
http://wingolog.org/