December 03, 2015 05:12AM
Thanks a lot for the clarification guys! :)



On Wed, Dec 2, 2015 at 7:46 PM, itpp2012 <nginx-forum@nginx.us> wrote:

> Richard Stanway Wrote:
> -------------------------------------------------------
> > TCP has no concept of server names, so this is not possible. It only
> > works
> > in HTTP because the client sends the hostname it is trying to access
> > as
>
> To put into better wording,
> The 'hostname' technique has 2 parts, part 1 is a receiver (nginx)
> receiving
> a request containing a hostname which it can match (or not) to an item in
> its configuration, and part 2 the DNS name where this name is recorded
> against its IP address. With stream{} you can only rely on part 2.
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,263208,263219#msg-263219
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

server_name within tcp server blocks

cprenzberg December 02, 2015 06:32AM

Re: server_name within tcp server blocks

Richard Stanway December 02, 2015 01:18PM

Re: server_name within tcp server blocks

itpp2012 December 02, 2015 01:46PM

Re: server_name within tcp server blocks

cprenzberg December 03, 2015 05:12AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 263
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