Hello!

On Thu, Aug 12, 2010 at 12:09:02PM -0700, Matthieu Tourne wrote:

> Hi,
>
> I kept seeing "upstream sent unsupported FastCGI protocol version" in
> my error logs, and they went away when I turned fastcgi_cache off.
> It turned out that the files holding the cache were corrupted,
> starting at random places instead of the FastCGI headers.
>
> After trying to tweak things every possible way, I finally found out
> that the errors seemed to go away if I didn't use
> fastcgi_cache_bypass.
> And later on, I realized that when using fastcgi_no_cache with the
> same variable as for fastcgi_cache_bypass, I don't get any of those
> errors, and it works as intended.
>
> I saw in the source that a warning was added recommending to use
> fastcgi_cache_bypass when fastcgi_no_cache is used, but not the other
> way around.

This warning is about fastcgi_no_cache semantics change
(previously it was doing both _no_cache and _cache_bypass things).

> Should they always be used together, or is this a bug ?

Sounds like a bug.

Maxim Dounin

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