On Wed, Dec 12, 2012 at 11:43 AM, José Francisco Álvarez Aguilar
wrote:
> 2012/12/12 Tom Evans
>>
>> It "works" just fine, you are just not understanding what is necessary
>> for it to work.
>>
>> VirtualHost uses the Host header supplied in the request to best
>> determine the website to route t
2012/12/12 Tom Evans
> It "works" just fine, you are just not understanding what is necessary
> for it to work.
>
> VirtualHost uses the Host header supplied in the request to best
> determine the website to route the request to.
>
> In order to read headers in an SSL request you need to decrypt
On Wed, Dec 12, 2012 at 9:30 AM, José Francisco Álvarez Aguilar
wrote:
> Yes, www1.example.com, www2.example.com and wwwsecure.example.com all
> resolve to the same IP.
> So, due to your explanation, I can't have different behaviour for this 3
> virtualhosts without using different certificates or
Yes, www1.example.com, www2.example.com and wwwsecure.example.com all
resolve to the same IP.
So, due to your explanation, I can't have different behaviour for this 3
virtualhosts without using different certificates or without using SNI.
But there's one thing I don't understand: if we use "virtual
On Thu, Dec 6, 2012 at 7:59 PM, Pepe wrote:
> I have an apache server with 3 virtual host (all DNS work already done):
> http://www1.example.com --> listens on port 80
> http://www2.example.com --> listens on port 80 with required user
> authentication
> https://wwwsecure.example.com --> listens o
I have an apache server with 3 virtual host (all DNS work already done):
http://www1.example.com --> listens on port 80
http://www2.example.com --> listens on port 80 with required user authentication
https://wwwsecure.example.com --> listens on port 443
Everyone with different DocumentRoot.
Ever
