Hi guilers, 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].
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. Patches are supplied for both. [0]. https://tools.ietf.org/html/rfc822#section-5.1 (see 1*2DIGIT) [1]. Be conservative in what you send; be liberal in what you accept. -- Ian Price "Programming is like pinball. The reward for doing it well is the opportunity to do it again" - from "The Wizardy Compiled"
