Nginx-ru mailing list archive (nginx-ru@sysoev.ru)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rewrite / proxy_pass different bahaviour in 1.0 and 1.2
- To: nginx-ru@xxxxxxxxx
- Subject: Re: rewrite / proxy_pass different bahaviour in 1.0 and 1.2
- From: "alexey.radkov" <nginx-forum@xxxxxxxx>
- Date: Sat, 29 Sep 2012 09:33:00 -0400
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tigger.jlkhosting.com; s=x; h=Date:Sender:From:References:In-Reply-To:Message-ID:Content-Transfer-Encoding:Content-Type:Subject:To; bh=L/ifa1sdEp874AdnF07XtS9aLmVn59Mz1BzoI8sDdRo=; b=SCyiR4nj+eYuZU3Uv/yhAQhISm83SNCIDfTlpxHAiL9tQCrEVrUmwxemFYNF+pfQFT5c99uhvTHE+uRBR0eJFWy8uwv3CkL3AGLGZN2GHRcZoAGhxUoYq21ESp0f4v2R;
- In-reply-to: <20120928175832.GN40452@mdounin.ru>
- References: <20120928175832.GN40452@mdounin.ru>
Maxim, thank you!
This "bug" was a "feature" in our own proxy module based upon standard nginx
proxy module. When i ported changes in 1.2 into our module i was surprised
why some of our rules were not working until i found this change.
We cannot use something like
proxy_pass http://$arg_a$request_uri;
because our directives do not support this. So currently i just reverted
those 2 removed lines into our module. May i expect some unwanted side
effects from thÕ removal except those which we are using as "feature"?
Cheers, Alexey.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?21,231218,231247#msg-231247
_______________________________________________
nginx-ru mailing list
nginx-ru@xxxxxxxxx
http://mailman.nginx.org/mailman/listinfo/nginx-ru
|
