Hello,
yes that is indeed possible with nginx.
The Admin Guide is a good starting point:
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
The principal module you'll be dealing with is the http_proxy module, you can
find the docs here:
https://nginx.org/en/docs/http/ngx_http_p
On 11/23/18 3:11 PM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Nov 23, 2018 at 09:23:01AM +0100, Jack Henschel wrote:
>
>> Hi Maxim,
>>
>> thanks for the quick confirmation!
>>
>>> The Host header is set to what you wrote in the "proxy_pass"
nt
certificates.
2. Upstream vhosts. Consider the scenario where multiple domains point to the
same IP address, where the requests are split apart based on the Host header
(I.e. virtual hosts)
What do you think?
Regards
Jack
On 22 November 2018 22:13:38 CET, Maxim Dounin wrote:
>Hello!
>
Hello everyone,
during my last debugging session with Nginx I was wondering how and when
exactly Nginx passes upstream's hostname when proxying a request.
In particular, I have the following example:
> upstream backend {
> server a.example.com:443;
> server b.example.com:443;
> }
> server {