Why does this URL result in a 400 (Bad Request) error?
grails at jmsd.co.uk
Wed Nov 4 16:45:53 MSK 2009
John Moore wrote:
> Igor Sysoev wrote:
>> Have this resolved Tomcat issue ? It's really strange that Tomcat
>> does not
>> support the encoded URL.
> It seems to have done, yes. It's had a slight side-effect, though, in
> that I'm now getting a 404 error from nginx on a particular page,
> which it should be proxying. How would the addition of the forward
> slash to http://backend cause this, and what do I need to do to
Ignore this, it was simply because another block was also using the
proxy module and I hadn't updated it. It did confirm, though, that the
proxy_pass directive is very fussy about where it is. In this block, if
I append an / to the http://backend, it gives the same error as reported
earlier ("proxy_pass" may not have URI part in location given by regular
expression, or inside named location, or inside the "if" statement, or
inside the "limit_except" block in /etc/nginx/nginx.conf:98):
As it happens, I don't actually need the encoding/decoding working for
these pages, so I can leave it as it is above.
More information about the nginx