Hello list,
in Ticket #196 [1], Maxim Dounin suggested that spaces in URI's could be
disallowed by default.
As far as I can tell, current code still does not "disallow" those requests
(not by default and not via specific configuration either), is that correct?
Could this be improved, as per t
Hi All.
I have been trying to do url-based redirections, but as per
http://mailman.nginx.org/pipermail/nginx/2017-April/053443.html, there are
issues cropping up.
If the issues exist, then I will have to follow the
one port for each proxy-url (constant "/" location)
approach, instead of
The same thing works if I put "/" in the location.
The URL-change is the same, and things work seamlessly.
It is definitely something that I am missing while specifying a location
other than "/", that is causing incomplete proxying under the hood.
On Sat, Apr 8, 2017 at 7:10 PM, Anoop Alias wrot
The 404 is thrown by whatever is working on port 2000 ;so you can check its
access log and see
On Sat, Apr 8, 2017 at 6:54 PM, Ajay Garg wrote:
> Hi Anoop.
>
> As per http://serverfault.com/questions/379675/nginx-
> reverse-proxy-url-rewrite, the rewrite should be automatic.
> But it does not w
Hi Anoop.
As per
http://serverfault.com/questions/379675/nginx-reverse-proxy-url-rewrite,
the rewrite should be automatic.
But it does not work for me :(
On Sat, Apr 8, 2017 at 6:49 PM, Anoop Alias wrote:
> I think you are confusing between url-rewrite and location
>
> On Sat, Apr 8, 2017 at 6:
I think you are confusing between url-rewrite and location
On Sat, Apr 8, 2017 at 6:39 PM, Ajay Garg wrote:
> Hi All.
>
> When I setup the following, the authentication+proxying works perfect,
> with the url changing from http://1.2.3.4:2001 to
> http://1.2.3.4:2001/cgi-bin/webproc, and the prox
Hi All.
When I setup the following, the authentication+proxying works perfect, with
the url changing from http://1.2.3.4:2001 to
http://1.2.3.4:2001/cgi-bin/webproc, and the proxied0server opening up
perfectly.
server {
On Sat, Apr 08, 2017 at 08:46:57AM +0100, Musta Fa wrote:
Hi there,
> but i can not make it listen on custom_ip:80
> port 80 is always 0.0.0.0:80
>
> cd /etc/nginx
> grep listen -r *
> only "listen custom_ip:80;"
>
> why is that??
Any server{} without an explicit "listen" has an implicit "list
nginx/1.11.13
i have 4 server IPs, all registered in network interface
and many domains and apps, also on different ports.
all other ports are ok:
custom_ip1:443, custom_ip1:5000, custom_ip1:81
custom_ip2:443, custom_ip2:5000, custom_ip2:81
custom_ip3:443, custom_ip3:5000, custom_ip3:81
but i c
