t 17.37
> To: "nginx@nginx.org"
> Subject: Re: URL-Rewriting not working
>
> Hi Francis.
>
> On Sun, Apr 9, 2017 at 8:47 PM, Francis Daly wrote:
>
>> On Sun, Apr 09, 2017 at 06:36:51PM +0530, Ajay Garg wrote:
>
-boun...@nginx.org>> on behalf
of Ajay Garg mailto:ajaygargn...@gmail.com>>
Reply-To: "nginx@nginx.org<mailto:nginx@nginx.org>"
mailto:nginx@nginx.org>>
Date: Sunday, 9 April 2017 at 17.37
To: "nginx@nginx.org<mailto:nginx@nginx.org>"
mailto:nginx@nginx.o
Hi Francis.
On Sun, Apr 9, 2017 at 8:47 PM, Francis Daly wrote:
> On Sun, Apr 09, 2017 at 06:36:51PM +0530, Ajay Garg wrote:
>
> Hi there,
>
> > Got it Francis !!
>
> Good news.
>
> > location / {
> > auth_basic 'Restricted';
> >
On Sun, Apr 09, 2017 at 06:36:51PM +0530, Ajay Garg wrote:
Hi there,
> Got it Francis !!
Good news.
> location / {
> auth_basic 'Restricted';
> auth_basic_user_file
> /home/20da689b45c84f2b80bc84d651
Got it Francis !!
server {
listen 2001 ssl;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
location / {
auth_basic 'Restricted';
Hi Francis.
Thanks a ton for your suggestions.
On Sun, Apr 9, 2017 at 5:58 PM, Francis Daly wrote:
> On Sun, Apr 09, 2017 at 05:27:31PM +0530, Ajay Garg wrote:
>
> Hi there,
>
> > Unfortunately, our backen-service(s) (on port 2000 in the example) is
> > ssh-reverse-tunnel, having two layers of
On Sun, Apr 09, 2017 at 05:27:31PM +0530, Ajay Garg wrote:
Hi there,
> Unfortunately, our backen-service(s) (on port 2000 in the example) is
> ssh-reverse-tunnel, having two layers of machines behind them. The
> terminating-node for sure cannot be changed.
"In general", reverse-proxying to a dif
Hi Francis.
Thanks for your detailed analysis.
Unfortunately, our backen-service(s) (on port 2000 in the example) is
ssh-reverse-tunnel, having two layers of machines behind them. The
terminating-node for sure cannot be changed.
Looking at your explanations, I guess then we will have to open a p
On Sat, Apr 08, 2017 at 06:39:59PM +0530, Ajay Garg wrote:
Hi there,
> However, I am not able to do the proxying if I perform url-rewriting.
> Nothing of the following works ::
Note that if you want to reverse-proxy a back-end web service at a
different part of the url hierarchy to where it beli
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 {
14 matches
Mail list logo
