16 messages in ru.sysoev.nginxRe: Mixed Virtualhosts and IP hosts
FromSent OnAttachments
DavidAug 30, 2008 8:02 pm 
mikeAug 30, 2008 8:18 pm 
Igor SysoevAug 30, 2008 11:34 pm 
Igor SysoevAug 30, 2008 11:35 pm 
mikeAug 30, 2008 11:58 pm 
Igor SysoevAug 31, 2008 12:17 am 
Igor SysoevAug 31, 2008 12:22 am 
mikeAug 31, 2008 12:29 am 
Igor SysoevAug 31, 2008 12:30 am 
mikeAug 31, 2008 12:31 am 
mikeAug 31, 2008 12:37 am 
Scott LarsonAug 31, 2008 12:59 am 
mikeAug 31, 2008 1:18 am 
Scott LarsonAug 31, 2008 1:52 am 
mikeAug 31, 2008 1:58 am 
DavidAug 31, 2008 6:13 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Mixed Virtualhosts and IP hostsActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Aug 31, 2008 12:22:47 am
List:ru.sysoev.nginx

On Sun, Aug 31, 2008 at 11:17:50AM +0400, Igor Sysoev wrote:

On Sat, Aug 30, 2008 at 11:58:39PM -0700, mike wrote:

On 8/30/08, Igor Sysoev <is-G@public.gmane.org> wrote:

I never tried several http {} blocks, and I'm not sure that it will work correctly.

really? works fine from my perspective - here's my config. seems to work great. i thought that was the whole point, is you can have multiple services as needed (http, imap or whatever, etc) - i guess i'd take any optimization pointers, i'm always interested in simplifying configurations and optimization!

You may use http and main sections in one configuraiton, but several http's are not intended by design. Probably they sould work, I will investigate.

I have found the case that will not work: in the following configuration all requests to 80 port will go to one server only, despite the Host header:

http { server { listen 80; server_name one; } }

http { server { listen 80; server_name two; } }

So several http{} sections are not supported configuration.