NGINX: Set/use requests with fully qualified domain name (= FQDN).
Francis Daly
francis at daoine.org
Wed May 11 22:28:10 UTC 2016
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 at daoine.org
More information about the nginx
mailing list