On Mon, Apr 17, 2017 at 11:19:36AM +0530, Ajay Garg wrote:
Hi there,
> I created two different credentials, one which forwards via http-protocol,
> and the other which forwards via https-protocol.
Good that you came up with a system that works.
Cheers,
f
--
Francis Dalyfran...
On Sun, Apr 16, 2017 at 09:49:09AM +0530, Ajay Garg wrote:
> 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,
> Proxy-Server and Gateway are connected via a ssh-reverse-tunnel.
> The port over which they are connected r
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 Francis.
>
> Thanks
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 upstream-server, the request su
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 upstream-server, the request suitably returns a 502 error. More
> importantly, the $arg_upstream_protocol does seem to be parsed properly ::
Hi Francis.
I tried the curl method, and I happened to land on an interesting
observation.
a)
If there is no forwarded-port in listening state (port 5000 in this case)
for the upstream-server, the request suitably returns a 502 error. More
importantly, the $arg_upstream_protocol does seem to be p
On Fri, Apr 14, 2017 at 06:42:22PM +0530, Ajay Garg wrote:
Hi there,
> When I do the following call ::
>
> https://username:password@1.2.3.4?upstream_protocol=http
> 2017/04/14 13:03:51 [error] 16039#16039: *1 invalid URL prefix in "://
> 127.0.0.1:5000", client: 182.69.5.226, server: , request
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
