[Mongrel] Invalid HTTP format, parsing fails
ross.singer at library.gatech.edu
Fri Aug 25 15:49:25 EDT 2006
While I agree with this fundamentally, pragmatically this is an unrealistic
expectation. I get this vendor to fix it, another vendor pops up with
another dumb unescaped character.
You can type these characters into the query string on IE or Safari and get
the same result, it wouldn't have to be vendor provided.
I am not 'blaming' anybody. I'm just pointing out that it's a pretty
chaotic world and, as a result, it's fairly important that (within reason) a
webserver can handle the things that are thrown at it.
My webserver is the one thing that /I/ can control.
On 8/25/06, snacktime <snacktime at gmail.com> wrote:
> You can't really blame mongrel for a bug in someone elses code. Zed
> is very clear on the website that the parser is strict. Properly
> urlencoding the query string is basic web programming 101 stuff. If
> it was me I would be nice but make it clear to your vendor that this
> is really just not acceptable and you expect to have it fixed asap.
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mongrel-users