Package: nginx
Version: 1.6.2-5
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Having a rule like so in the nginx configuration
location ^~ /foo/bar/news.php {
if ($arg_id ~ [0-9]+) {
We would need to see your entire unmodified configuration file to help
with this. Additionally, it is MUCH better to use a map directive for
most cases where $arg_ARG is used.
On Wed, Jun 10, 2015 at 7:53 AM, Carsten Klein
carsten.kl...@bva-media.de wrote:
Package: nginx
Version: 1.6.2-5
System
Betreff: Re: Bug#788348: nginx: $arg_id is always undefined
We would need to see your entire unmodified configuration file to help with
this. Additionally, it is MUCH better to use a map directive for most cases
where $arg_ARG is used.
On Wed, Jun 10, 2015 at 7:53 AM, Carsten Klein
:81/loc3?id=12name=foo
TIA for your help!
Carsten
-Ursprüngliche Nachricht-
Von: Michael Lustfield [mailto:mich...@lustfield.net]
Gesendet: Mittwoch, 10. Juni 2015 15:38
An: Carsten Klein; 788...@bugs.debian.org
Cc: Debian Bug Tracking System
Betreff: Re: Bug#788348: nginx: $arg_id
severity 788348 wishlist
tags 788348 help
stop
As that server block is written, nginx will not start due to
configuration errors. It appears that you should indeed be using a map
for your test. Additionally, you're trying to use the same
$arg_PARAMETER twice for the same request which will not
5 matches
Mail list logo
