Re: Regarding URL Encode/Decode of the Parameter

2017-07-28 Thread m.i
As I invetsgate more, as you pointed out, I found Nginx is working as expected. It does not apply url encoding to what already has been url encoded. So, Nginx is good. I mean, great! We had another proxy before Nginx and it was making the url encoding issue. Thank you for pointing out for me to s

redirect related questions...

2017-07-28 Thread ST
Hello, I have several questions related to redirects: Here is my setup: server { server_name www.example.org example.com; # and some more domains return 301 $scheme://example.org$request_uri; } server { listen 80; server_name example.org; ... if ($http_user_agent !~ facebookexternalhit/1.

Re: Regarding URL Encode/Decode of the Parameter

2017-07-28 Thread Francis Daly
On Fri, Jul 28, 2017 at 04:30:33AM -0400, m.i wrote: Hi there, > > server { > listen 8881; > server_name localhost; > > location / { > proxy_pass http://111.111.111.111; > } > } > When I use this (proxy_pass:ing to an address:

Re: Regarding URL Encode/Decode of the Parameter

2017-07-28 Thread m.i
Hello, thank you so much for your post. Below is the configuration I'm using. It's pretty much straight forward. I just want to transfer the massage using "proxy_pass." server { listen 8881; server_name localhost; location / { proxy_pass http://111.111.1

Re: Regarding URL Encode/Decode of the Parameter

2017-07-28 Thread Francis Daly
On Thu, Jul 27, 2017 at 11:44:29PM -0400, m.i wrote: Hi there, > Now, I noticed that Nginx applies url encode to % and make it as %25 when it > redirect the message. The parameter now become below. > GET /X/Y/Z.aspx?id=abc%253D%253D > > I want Nginx to redirect the parameter as is. Below is the

Re: Problem with uWSGI and PATH_INFO

2017-07-28 Thread Roberto De Ioris
> Hi Roberto, > > Le 2017-07-27 à 13:45, Roberto De Ioris a écrit : >> >> by using something like this (in the config, tune the regexps as >> required): >> >> [uwsgi] >> route = ^/(.+?)/(.+)$ setscriptname:/$1 >> route = ^/(.+?)/(.+)$ setpathinfo:/$2 >> > I use a dynamic regex URL resolver to reso

Re: nginx 1.13 binaries

2017-07-28 Thread Francis Daly
On Thu, Jul 27, 2017 at 02:47:01PM -0400, Gee Bunny wrote: Hi there, > There might be talk of binaries being available on the page you > linked, but if you check the repo link I provided (to the NGINX hosted > YUM Repository for CentOS 6 x86_64) there's no version 1.13 it goes as > high as nginx-

Re: Problem with uWSGI and PATH_INFO

2017-07-28 Thread Francis Daly
On Thu, Jul 27, 2017 at 12:06:42PM -0400, Etienne Robillard wrote: > Le 2017-07-27 à 11:25, Francis Daly a écrit : > >On Thu, Jul 27, 2017 at 07:45:28AM -0400, Etienne Robillard wrote: Hi there, > >The uwsgi_params values are an example of what can be done. The > >combination of SCRIPT_NAME and P

Accessing Nginx Cache mappings

2017-07-28 Thread Gryzli Bugbear
Hi guys, I'm trying to implement cache-purger, which is using lua and separate VirtualHosts, to clean the cache for a certain site/location based on URI regex (similar to Varnish). Is there some easy way (module/function or whatever), by which I could access the internal Nginx cache mapping