Francis Daly
May 11, 2016 06:30PM
On Wed, May 11, 2016 at 07:24:09AM -0400, Sportmodus wrote:

Hi there,

> Now I want to proxy_pass an external server and I have to use our proxy for
> this to get an external connection.

Stock nginx does not speak proxy-http to a proxy server.

> Can I modify this to
>
> "GET http://external.com:80/uri HTTP/1.1
> HOST: external.com"
>
> ?

Only if you arrange for the code to do it be written.

If you choose to write it fully, it might be welcomed into stock nginx.

> Problem is: Our proxy denies requests (error 400 bad request) without FQDN
> (= fully qualified domain name).

Your proxy is correct to do so.

It just expects a protocol that nginx does not speak.

> Any help or workaround is welcome.

Use something that can be a proxy client, and use it instead of (or as
well as) nginx.

Or, since nginx is a reverse proxy, and you only reverse proxy for things
you control, change your policy so that nginx can talk to your external
web server without going through the proxy.

I don't think that there is a "good" answer.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

NGINX: Set/use requests with fully qualified domain name (= FQDN).

Sportmodus May 11, 2016 07:24AM

Re: NGINX: Set/use requests with fully qualified domain name (= FQDN).

Francis Daly May 11, 2016 06:30PM

Re: NGINX: Set/use requests with fully qualified domain name (= FQDN).

Sportmodus May 13, 2016 04:30AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 280
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready