Sorry, turns out this was an issue in Jetty, not nginx. Bug is here: http://jira.codehaus.org/browse/JETTY-336by dobesv - How to...
On further investigation I think it is the referer: header that is causing the request to be rejected; the referer when using chrome is a long URL but in IE it is a shorter value. Here's the actual raw requests: Chrome (rejected): GET /app/report?format=xmlswf&chart=true&nocache=1264228009320&chart_type=line&skip=16&line_thickness=2&point_size=3&fill_shape=trueby dobesv - How to...
Hi there, I have a flash widget that uses a really long 1400 character URI to fetch it's data. For some reason nginx is returning an error 413 back when I try to use this in Chrome. This used to affect all browsers but I bumped the buffers and that fixed it for everyone else. However, for Google Chrome I'm still seeing this. The request is supposed to be proxied via HTTP to a Jetty baby dobesv - How to...