Re: -pass-headers

Janis Volbergs schrieb:
> Actually ALL the headers are being passed to the underlying fastcgi 
> program.  There is, however, a slight difference when working with HTTP
> authorization data.
> You shouldn't bother about it.

Does that mean that I can bet real money that
   -pass-header Authorization
is all that I ever need?

Because this is exactly the bet I'm placing if I accept this advice :-)

 > In case your customers are claiming that
> something is wrong, perhaps, they could specify which "headers" are not 
> being received.
> Then it would be possible to make more thorough analysis.

I vastly prefer analysis *before* things break.

That won't prevent all problems, but it can reduce their number.
And every problem prevented before it happens is one unhappy customer 
less :-)

> Oh yes, and most of the "headers" are being stored as environment 
> variables. E.g. accesible via getenv or similar function call (at least 
> in C) (e.g. getenv("QUERY_STRING"), getenv("HTTP_REFERER") and whatever 
> else..

Ah, right. I was still thinking in terms of mod_php, which has direct 
access to the headers.
PHP scripts can access environment variables through a global 
associative array, so no problems there.

Of course, since scripts are now running from CGI rather than from 
within an Apache module, they might find the header data in different 
locations than before. The CGI version of PHP tries to cover up for the 
differences; as for those that remain: well, I don't guess that's the 
domain of fastcgi expertise anyway :-)

Regards,
Jo

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/