Never mind.
I created two different credentials, one which forwards via http-protocol,
and the other which forwards via https-protocol.
Thanks everyone (especially Francis) for all the help !!!
Thanks and Regards,
Ajay
On Sun, Apr 16, 2017 at 9:49 AM, Ajay Garg wrote:
> Hi Fran
Hi Francis.
Thanks for your continued help.
On Sat, Apr 15, 2017 at 8:50 PM, Francis Daly wrote:
> On Sat, Apr 15, 2017 at 02:47:26PM +0530, Ajay Garg wrote:
>
> Hi there,
>
> > If there is no forwarded-port in listening state (port 5000 in this case)
> > for the upst
seems I
need to do some url-rewritings while the requests move to and from between
nginx and upstream-server, right?
On Sat, Apr 15, 2017 at 1:55 PM, Francis Daly wrote:
> On Fri, Apr 14, 2017 at 06:42:22PM +0530, Ajay Garg wrote:
>
> Hi there,
>
> > When I do the following c
just as
> safe as any other method as long as it's going over HTTPS, and the
> credentials should never appear in any access logs (unless you specifically
> choose to log the Authorization header).
>
> On Fri, Apr 14, 2017 at 6:47 AM, Ajay Garg wrote:
>
>> Hi Ri
Hi All.
When I do the following call ::
https://username:password@1.2.3.4?upstream_protocol=http
I get a 500 error (on the browser-client), with the following seen in
/var/log/nginx/error.log (on nginx-server)
##
2017/04/14 13:03:51 [error] 1
ively pass the basic auth in your URI, eg xhr.open("GET", "
> https://username:password@1.2.3.4/";) rather than crafting it manually.
>
> On Thu, Apr 13, 2017 at 4:50 PM, Ajay Garg wrote:
>
>> Strange, but rebooting the machine caused the credentials-popup to be
Strange, but rebooting the machine caused the credentials-popup to be
seen again :-|
Sorry for the noise here.
There has been some progress, but still get a "CORS preflight did not
succeed error".
Following is what I am doing.
a)
Following is the server-block in /etc/nginx/conf.d/default.conf ::
er 'Access-Control-Allow-Credentials'
'true';
# proxy_set_header 'Access-Control-Allow-Methods'
'GET, POST, OPTIONS';
# proxy_set_header 'Access-Control-Allow-Headers'
'DNT,X-CustomHeader,Keep-Alive,User
use "always" if you want to include the header
> in all responses. See the documentation for more details.
>
> http://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header
>
> On Wed, Apr 12, 2017 at 4:48 PM, Ajay Garg wrote:
>
>>
low-Credentials'
'true';
proxy_set_header 'Access-Control-Allow-Methods'
'GET, POST, OPTIONS';
proxy_set_header 'Access-Control-Allow-Headers'
'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-Wit
Sorry for the idiotic question.
Just checked, multiple sockets are created on each side of the ssh-reverse
tunnel.
So, seems the 502-Bad-Gateway error is due to other (network-slowness)
issues.
Sorry again.
Thanks and Regards,
Ajay
On Wed, Apr 12, 2017 at 12:38 PM, Ajay Garg wrote:
> Hi
Hi All.
We are facing the following issue :
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the
remote resource at https://1.2.3.4/. (Reason: CORS header 'Access-Control-
Allow-Origin' missing).
Have tried everything I could find on the google, but nothing works
(whatever
Hi All.
Let's say, we have a server-block like
server {
listen 2001 ssl;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
st you take a look at everything: https://nginx.org/en/docs/
>
Thanks B.R., I surely will !!
> ---
> *B. R.*
>
> On Sun, Apr 9, 2017 at 4:25 PM, Ajay Garg wrote:
>
>> Thanks a ton Lucas.
>>
>> Just checked reloading, and the previous proxy-session was intact !
ou're trying to do, using a map would be the cleanest (and
> nicest) way I believe – someone can correct me if they want :-D
>
> From: nginx on behalf of Ajay Garg <
> ajaygargn...@gmail.com>
> Reply-To: "nginx@nginx.org"
> Date: Sunday, 9 April 2017 a
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 / {
> >
ime involved in this process.
>
>
> From: nginx on behalf of Ajay Garg <
> ajaygargn...@gmail.com>
> Reply-To: "nginx@nginx.org"
> Date: Sunday, 9 April 2017 at 15.55
> To: "nginx@nginx.org"
> Subject: Mechanism to avoid restarting nginx upon ev
Hi All.
We are wanting to implement a solution, wherein the user gets proxied to
the appropriate local-url, depending upon the credentials.
Following architecture works like a charm (thanks a ton to
fran...@daoine.org, without whom I would not have been able to reach here)
::
tps://127.0.0.1:2000;
}
}
}
Love you !!! :P :P
Thanks and Regards,
Ajay
On Sun, Apr 9, 2017 at 6:16 PM, Ajay Garg wrote:
> Hi Francis.
>
> Thanks a ton for your suggestions.
>
> On Sun, Apr 9, 2017 at 5:58 PM, Francis Daly wrote:
>
>&
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-tunn
-April/053448.html. If there
isn't an issue with opening multiple nginx-listening-ports to the public,
then I guess we are done.
Would love to hear back your thoughts.
Thanks and Regards,
Ajay
On Sun, Apr 9, 2017 at 4:19 PM, Francis Daly wrote:
> On Sat, Apr 08, 2017 at 06:39:59PM +05
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
7:10 PM, Anoop Alias wrote:
> 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-revers
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
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 {
out as to how to specify
username:password on the URL basis.
Thanks and Regards,
Ajay
On Fri, Apr 7, 2017 at 7:15 PM, Ajay Garg wrote:
> Hi All.
>
> We have setup multiple ssh-reverse tunnels, and our server will be
> listening to ports from 9000 to 1.
> The server will h
Hi All.
We have setup multiple ssh-reverse tunnels, and our server will be
listening to ports from 9000 to 1.
The server will have a public-IP, and we DO NOT want just anyone to look
into any of the ports by trying ::
http://1.2.3.4:9000
http://1.2.3.4:9001 and so on ...
So, we are wonderin
27 matches
Mail list logo
