server_name within tcp server blocks
Charles Nnamdi Akalugwu
cprenzberg at gmail.com
Thu Dec 3 10:11:19 UTC 2015
Thanks a lot for the clarification guys! :)
On Wed, Dec 2, 2015 at 7:46 PM, itpp2012 <nginx-forum at 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 at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20151203/c8222691/attachment.html>
More information about the nginx
mailing list