Does anyone know where I can find a list of the variables used in nginx? I know the following are available: $http_host $uri Are there any others? -- *Phillip B Oldham* The Activity People phill@theactivitypeople.co.uk <mailto:phill@theactivitypeople.co.uk> ------------------------------------------------------------------------ *Policies* This e-mail and its attachments are intended for the above named recipient(s) only and may be confidential. If they have come to you in error, please reply to this e-mail and highlight the error. No action should be taken regarding content, nor must you copy or show them to anyone. This e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium, and we have taken steps to ensure that this e-mail and attachments are free from any virus. We must advise that in keeping with good computing practice the recipient should ensure they are completely virus free, and that you understand and observe the lack of security when e-mailing us.
on 07.05.2008 09:54
on 07.05.2008 10:05
The wiki (http://wiki.codemongers.com/) has most things documented, but there isn't a list of variables per se - just the variables listed when you read about a specific feature.
on 07.05.2008 10:12
Phillip B Oldham wrote: > Does anyone know where I can find a list of the variables used in nginx? > > I know the following are available: > $http_host > $uri > > Are there any others? Main ones are described here: http://wiki.codemongers.com/NginxHttpCoreModule You have also some more in the wiki depending on the modules.
on 07.05.2008 10:12
I've found a list in http://wiki.codemongers.com/NginxHttpCoreModule, but it doesn't seem to be complete (no $http_host). I think it would be useful if we had all the variables documented. mike wrote: >> I know the following are available: >> ------------------------------------------------------------------------ >> this e-mail and attachments are free from any virus. We must advise that in > -- *Phillip B Oldham* The Activity People phill@theactivitypeople.co.uk <mailto:phill@theactivitypeople.co.uk> ------------------------------------------------------------------------ *Policies* This e-mail and its attachments are intended for the above named recipient(s) only and may be confidential. If they have come to you in error, please reply to this e-mail and highlight the error. No action should be taken regarding content, nor must you copy or show them to anyone. This e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium, and we have taken steps to ensure that this e-mail and attachments are free from any virus. We must advise that in keeping with good computing practice the recipient should ensure they are completely virus free, and that you understand and observe the lack of security when e-mailing us.
on 07.05.2008 11:45
Hello! On Wed, May 07, 2008 at 09:01:52AM +0100, Phillip B Oldham wrote: > I've found a list in http://wiki.codemongers.com/NginxHttpCoreModule, but > it doesn't seem to be complete (no $http_host). > > I think it would be useful if we had all the variables documented. [quote from http://wiki.codemongers.com/NginxHttpCoreModule] First of all, these are the variables, which represent the lines of the title of the client request, for example, $http_user_agent, $http_cookie and so forth. [end quote] All headers sent by client are available through $http_* variables. Their existance isn't guaranteed and their meaning defined elsewhere (e.g. in relevant standards). Some more notes on variables in general: Any module can define its own variables, and so variables are usually documented in context of module which provides them. Maxim Dounin
on 07.05.2008 12:02
Maxim Dounin wrote: > All headers sent by client are available through $http_* variables. > Their existance isn't guaranteed and their meaning defined elsewhere > (e.g. in relevant standards). Ah, I see. Thanks for that. Maybe this should be stated in the wiki then? > Some more notes on variables in general: > > Any module can define its own variables, and so variables are usually > documented in context of module which provides them. I'll bear that in mind. Thanks again. -- *Phillip B Oldham* The Activity People phill@theactivitypeople.co.uk <mailto:phill@theactivitypeople.co.uk> ------------------------------------------------------------------------ *Policies* This e-mail and its attachments are intended for the above named recipient(s) only and may be confidential. If they have come to you in error, please reply to this e-mail and highlight the error. No action should be taken regarding content, nor must you copy or show them to anyone. This e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium, and we have taken steps to ensure that this e-mail and attachments are free from any virus. We must advise that in keeping with good computing practice the recipient should ensure they are completely virus free, and that you understand and observe the lack of security when e-mailing us.
on 07.05.2008 12:26
Hello! On Wed, May 07, 2008 at 10:52:01AM +0100, Phillip B Oldham wrote: > Maxim Dounin wrote: >> All headers sent by client are available through $http_* variables. Their >> existance isn't guaranteed and their meaning defined elsewhere (e.g. in >> relevant standards). > Ah, I see. Thanks for that. Maybe this should be stated in the wiki then? This is what wiki basically states but in shorter form. ;-) Feel free to change wording if you think current description isn't complete enough. Maxim Dounin