Hello!

On Thu, Apr 07, 2011 at 11:28:45AM -0400, cromulus wrote:

> I figured it out.
>
> Here is the problem: if the fastcgi_cache_bypass directive is below the
> fastcgi_cache_key directive, you encounter this particular problem.
> Moving the fastcgi_cache_bypass directive above the fastcgi_cache_key
> directive solved the problem and now urls of any length are process
> correctly.

I believe the problem in your case is not order of directives, but
fastcgi_cache_bypass itself. It has known problem that it doesn't
work correctly (results in corrupted cache entries) unless the
same predicates are used in fastcgi_no_cache.

Maxim Dounin

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx