fastcgi, simply wrong

Maxim Dounin mdounin at
Fri Apr 25 12:02:34 MSD 2008


On Fri, Apr 25, 2008 at 01:11:26AM -0300, Alexandre Girao wrote:

>Hi folks,
>  i've just dedicated some hours upon the nginx behavior/source code
>(version 0.6.29, but also happens to 0.5.35)
>  towards fastcgi protocol and discovered that the requestId is fixed,
>it's simple always equal do 1, this break the

Since nginx doesn't send more than one request within single 
connection to FastCGI application - there is nothing wrong with 
requestId always being 1.

See for 
details.  Quote:

% The Web server re-uses FastCGI request IDs; the application
% keeps track of the current state of each request ID on a given
% transport connection.

>  the concurrency completely (as i've proved easily) and it also
>causes early closed connections from the web
>  server/client became out-of-sync with the request state in correctly
>implemented fastcgi applications, not
>  trying to be unpleasant, but i think that saying that nginx supports
>fastcgi can do more harm than good to

If you experience problems with this - it's likely due to problems
with FastCGI protocol implementation in your application.  The way 
how nginx talks to application may be not fastest one, but it's 
perfectly correct as far as I see.

Maxim Dounin

>  the project..  passing by just to say this, hope you guys find a 
>good solution, im out.
>fastcgi is a good thing, see (and think) for yourself
>"rationality and objectivity is greatly discredited in these days" --
>George Soros
>Alexandre Girao

More information about the nginx mailing list