Closed johnnyshields closed 10 years ago
@johnnyshields that's unrelated to utf8-cleaner. It's the result of a invalid combination of URL params, e.g. from a request like /index.php?_REQUEST=&_REQUEST[option]=com_content
. I think those are Joomla-style URLs. Rack chokes on the presence of both a simple value (the empty string) and nested, hash-style values in the same parameter (_REQUEST).
I think another little Rack middleware would be a nice solution to this common problem.
Installed UTF-8 cleaner, seems to have resolved UTF-8 conversion errors in request, but now I'm seeing the following occasionally. Wondering if anyone else has seen the same?