Your message dated Fri, 12 Jun 2015 12:46:42 -0500
with message-id
<CAL4L7=BG+ae3+Y5mNDgX37rvBuB1mQ_tAx=yrdx2hsugvcy...@mail.gmail.com>
and subject line
has caused the Debian Bug report #788354,
regarding AW: Bug#788348: nginx: $arg_id is always undefined
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
788354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788354
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nginx
Version: 1.6.2-5
Severity: important
See the attachment for a working configuration that exposes three different
locations using different rules, loc1, loc2 and loc3.
Using the following URLs, you can reproduce the erroneous behavior:
http://localhost:81/loc1?id=12&name=foo
http://localhost:81/loc2?id=12&name=foo
http://localhost:81/loc3?id=12&name=foo
TIA for your help!
Carsten
-----Ursprüngliche Nachricht-----
Von: Michael Lustfield [mailto:[email protected]]
Gesendet: Mittwoch, 10. Juni 2015 15:38
An: Carsten Klein; [email protected]
Cc: Debian Bug Tracking 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 <[email protected]>
wrote:
> 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]+") {
> rewrite ...;
> }
> }
>
> Please note that in older nginx versions this worked just fine. It
> seems that it was broken with the introduction of nginx 1.6.2 or the version
> before that.
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> I pointed my browser to http://localhost/foo/bar/news.php?id=1234.
>
> * What was the outcome of this action?
>
> In the error.log it says that the rule could not be applied and that
> $arg_id was undefined.
>
> * What outcome did you expect instead?
>
> $arg_id should have had the value 1234 and the rule should have been
> applied along with also the rewrite directive.
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: 8.1
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.18.9-x86_64-jb1 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages nginx depends on:
> ii nginx-full 1.6.2-5
>
> nginx recommends no packages.
>
> nginx suggests no packages.
>
> -- no debconf information
>
--- End Message ---
--- Begin Message ---
closing duplicate
--- End Message ---
