Thompson, David writes: > No, upstream needs to fix their invalid Content-Type header. We've > had this problem a few times, most recently with rubygems.org, and in > all cases we've gotten upstream to fix it. Strict header parsing can > seem like an issue at times, but it's really a very good feature that > the rest of the world seems to ignore. [0]
So this is less about this package itself but rather this general issue of parsing Content-Type headers, which has come up repeatedly... "Be conservative in what you do, be liberal in what you accept from others"... when it comes to the web, we should follow the Robustness Principle: https://en.wikipedia.org/wiki/Robustness_principle It's absolutely true that Guile should enforce producing correct HTTP requests and responses. But as much as it's irritating as schemers, probably the ultimate group of "do the right thing" if there ever was one in the programming world, if we cut off sites that do the slightly-wrong thing, we're cutting a lot of potential users from a lot of the web... making Guile a lot less attractive of a language for scraping, etc... We should at least provide some sort of option to permit fuzziness, or to convert incoming http requests to fill in some default value, or etc? - Chris
