On Mon, Apr 30, 2012 at 8:15 AM, Plüm, Rüdiger, Vodafone Group
ruediger.pl...@vodafone.com wrote:
-Original Message-
From: Kaspar Brand [mailto:httpd-dev.2...@velox.ch]
Sent: Sonntag, 29. April 2012 09:59
To: dev@httpd.apache.org
Subject: Re: [users@httpd] SNI with apache 2.4.1
-Original Message-
From: Kaspar Brand [mailto:httpd-dev.2...@velox.ch]
Sent: Sonntag, 29. April 2012 09:59
To: dev@httpd.apache.org
Subject: Re: [users@httpd] SNI with apache 2.4.1 reverse proxy
Whether that is desired or not probably depends on a judgement of
possible use cases
On 23.04.2012 17:11, Michael Weiser wrote:
I don't think so: I'm not directing the Proxy to connect to a different
host. I just make it send different SNI data to the configured backend
server and accept a different CN in the server's certificate.
I guess it boils down to the question of what
Hello Karspar,
Hi all,
On Wed, Apr 18, 2012 at 10:16:51AM +0200, Kaspar Brand wrote:
So implementation-wise this will most likely have two parts of code:
1. Determining the hostname to put into SNI data depending on
ProxyPreserveHost somewhere in the reverse proxy module.
2.
On 16.04.2012 16:47, Michael Weiser wrote:
So implementation-wise this will most likely have two parts of code:
1. Determining the hostname to put into SNI data depending on
ProxyPreserveHost somewhere in the reverse proxy module.
2. Putting that value into the SNI data in mod_ssl's
Hi,
On Tue, Apr 10, 2012 at 10:01:11AM +0200, Michael Weiser wrote:
A solution might be something like:
ProxyPass / https://www.example.com:12443/ no-sni
ProxyPassReverse / https://www.example.com:12443/ no-sni
, disabling SNI towards the backend server.
Or can I tell the 2.2.14 apache
On 04/16/2012 12:45 PM, Michael Weiser wrote:
that makes mod_ssl put the content of the host header into the sni data
structures instead of the hostname from the URL used in the
ProxyPass(Reverse) configuration itself. This way even name-based
virtual hosts should work behind the reverse
Hi there,
On Mon, Apr 16, 2012 at 01:45:16PM +0200, Peter Sylvester wrote:
that makes mod_ssl put the content of the host header into the sni data
structures instead of the hostname from the URL used in the
ProxyPass(Reverse) configuration itself. This way even name-based
virtual hosts
On Mon, Apr 16, 2012 at 3:47 PM, Michael Weiser
mich...@weiser.dinsnail.net wrote:
Hi there,
On Mon, Apr 16, 2012 at 01:45:16PM +0200, Peter Sylvester wrote:
that makes mod_ssl put the content of the host header into the sni data
structures instead of the hostname from the URL used in the
Hi Tom,
On Mon, Apr 16, 2012 at 04:02:00PM +0100, Tom Evans wrote:
This could be a side-effect of ProxyPreserveHost On since only with
ProxyPreserveHost On does it make any sense anyways. With
ProxyPreserveHost Off, the SNI data should contain the hostname from the
ProxyPassReverse
Hi Igor,
Hi Daniel,
On Mon, Apr 09, 2012 at 08:56:12AM -, Igor Gali? wrote:
Then it looks like mod_proxy_http determines the value for
proxy-request-hostname from the remote URL in ProxyPass, but is
passing on the Host header from the original request.
That would imply
On Tue, Apr 10, 2012 at 1:38 AM, Jie Gao j@sydney.edu.au wrote:
Hi All
Would it be possible to expand the scope of ProxyPreserveHost to Location?
Regards,
Jie
I don't understand; ProxyPreserveHost affects the proxying apache
server, and controls whether it rewrites the 'Host' header
- Original Message -
On 07.04.2012 00:34, Daniel Ruggeri wrote:
I wanted to bring this up here - seems like a few things are going
on
that are confusing to me. I'll try to look into it when time
becomes
available, but I thought someone might have an opinion off the bat.
Subject: Re: [users@httpd] SNI with apache 2.4.1 reverse proxy
X-Mailer: Zimbra 7.0.0_GA_3077 (ZimbraWebClient - FF3.0
(Linux)/7.0.0_GA_3077)
- Original Message -
On 07.04.2012 00:34, Daniel Ruggeri wrote:
I wanted to bring this up here - seems like a few things are going
14 matches
Mail list logo
