Christopher Allan Webber <[email protected]> skribis: > 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:
I agree with that. Now, if it turns out that in practice we encounter few misbehaving servers, as seems to be the case here, then I think it makes sense to contact their operators and see if they can fix it. Ludo’.
