Re: [users@httpd] SNI with apache 2.4.1 reverse proxy

2012-04-16 Thread Michael Weiser
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

Re: [users@httpd] SNI with apache 2.4.1 reverse proxy

2012-04-16 Thread Peter Sylvester
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

Re: svn commit: r1325632 - /httpd/httpd/trunk/config.layout

2012-04-16 Thread Igor Galić
- Original Message - Author: igalic Date: Fri Apr 13 07:21:46 2012 New Revision: 1325632 URL: http://svn.apache.org/viewvc?rev=1325632view=rev Log: Introduce Slackware layout. patch: Frank Gingras Modified: httpd/httpd/trunk/config.layout Can I Back-port this for our

Re: A bug with httpd-2.4.2 Win-x64

2012-04-16 Thread Guenter Knauf
Hi Bing, you did hit the apr list - I think this should go to the httpd list instead ... ;-) Am 16.04.2012 14:32, schrieb Bing Swen: After building the httpd-2.4.2 x64 binaries with VS2010, I encountered a runtime error in the module libhttpd.dll, which alerts that a heap corruption

Re: [VOTE] Release Apache httpd 2.4.2 as GA

2012-04-16 Thread Igor Galić
- Original Message - This is NOT the list for starting OS wars on. Could you please point me to the correct list for that kind of thing? (: i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D

Re: [RESULT] Re: [VOTE] Release Apache httpd 2.4.2 as GA

2012-04-16 Thread Igor Galić
+1 - Original Message - With 3+ +1 (binding) votes and no -1s, I call the vote CLOSED and PASSED. Thx to all testers! On Apr 5, 2012, at 8:24 AM, Jim Jagielski wrote: The pre-release test tarballs for Apache httpd 2.4.2 can be found at the usual place:

Re: CHANGES-FCGID is incorrect

2012-04-16 Thread Jeff Trawick
On Tue, Apr 10, 2012 at 12:35 AM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 4/9/2012 11:30 PM, William A. Rowe Jr. wrote: The patch does have value to a limited number of applications.  I even went as far as to put caviats in the docs, and a see-docs note to the directive cmd

Re: [VOTE] Release Apache httpd 2.4.2 as GA

2012-04-16 Thread William A. Rowe Jr.
On 4/16/2012 8:10 AM, Igor Galić wrote: - Original Message - This is NOT the list for starting OS wars on. Could you please point me to the correct list for that kind of thing? (: http://en.wikipedia.org/wiki/Talk%3AOperating_system_advocacy That's been asked before ;-P

Re: CHANGES-FCGID is incorrect

2012-04-16 Thread William A. Rowe Jr.
On 4/16/2012 8:16 AM, Jeff Trawick wrote: On Tue, Apr 10, 2012 at 12:35 AM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 4/9/2012 11:30 PM, William A. Rowe Jr. wrote: The patch does have value to a limited number of applications. I even went as far as to put caviats in the docs, and a

Re: [users@httpd] SNI with apache 2.4.1 reverse proxy

2012-04-16 Thread Michael Weiser
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

Re: [users@httpd] SNI with apache 2.4.1 reverse proxy

2012-04-16 Thread Tom Evans
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

Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Mikhail T.
If the SSL-certificate is the same for all named vhosts configured for the given IP-address/port-number combination, why can not the vhosts have different DocumentRoots and other settings? Thank you. Yours, -mi

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Reindl Harald
Am 16.04.2012 17:34, schrieb Mikhail T.: If the SSL-certificate is the same for all named vhosts configured for the given IP-address/port-number combination, why can not the vhosts have different DocumentRoots and other settings? because SSL was misdesigned years ago and the Host-Header

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Tom Evans
On Mon, Apr 16, 2012 at 4:34 PM, Mikhail T. mi+t...@aldan.algebra.com wrote: If the SSL-certificate is the same for all named vhosts configured for the given IP-address/port-number combination, why can not the vhosts have different DocumentRoots and other settings? Thank you. Yours,   -mi

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Mikhail T.
On 16.04.2012 11:40, Tom Evans wrote: They can. Excerpt from my httpd.conf: Your excerpt does not show different DocumentRoots -- nor any other settings... Could you show more contents? What is the Apache version you are using? In all my attempts, Apache a) issues a pointless warning about

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Eric Covener
No, this does not answer my question. In my scenario the SSL-certificate is the same for all vhosts concerned. So Apache could use that certificate to establish the SSL connection, and then parse the Host:-header to determine, which group of other (non-SSL) settings to apply to the request.

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Mikhail T.
On 16.04.2012 11:55, Eric Covener wrote: Got a pointer to your configuration? Well, the real one I was designing now uses a work-around (single vhost with mod_rewrite examining the Host-header and picking the proper subdirectore). Here is a mock one, that I'd rather be using -- instead of

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Tom Evans
On Mon, Apr 16, 2012 at 4:51 PM, Mikhail T. mi+t...@aldan.algebra.com wrote: On 16.04.2012 11:40, Tom Evans wrote: They can. Excerpt from my httpd.conf: Your excerpt does not show different DocumentRoots -- nor any other settings... Could you show more contents? What is the Apache version

RE: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Plüm , Rüdiger , Vodafone Group
Without a NameVirtualHost directive this cannot work as you intend. Add NameVirtualHost *:433 Regards Rüdiger From: Mikhail T. [mailto:mi+t...@aldan.algebra.com] Sent: Montag, 16. April 2012 18:07 To: dev@httpd.apache.org; cove...@gmail.com Subject: Re: Why aren't name-based vhosts not working

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Issac Goldstand
Are you sure that your client supports SNI? On 16/04/2012 19:21, Tom Evans wrote: On Mon, Apr 16, 2012 at 4:51 PM, Mikhail T. mi+t...@aldan.algebra.com wrote: On 16.04.2012 11:40, Tom Evans wrote: They can. Excerpt from my httpd.conf: Your excerpt does not show different DocumentRoots --

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Tom Evans
On Mon, Apr 16, 2012 at 5:25 PM, Issac Goldstand mar...@beamartyr.net wrote: Are you sure that your client supports SNI? This is not reliant on SNI. Cheers Tom

Re: Why aren't name-based vhosts not working properly under SSL?

2012-04-16 Thread Mikhail T.
On 16.04.2012 12:24, Plüm, Rüdiger, Vodafone Group wrote: Without a NameVirtualHost directive this cannot work as you intend. Add NameVirtualHost *:433 I see... I thought, I'm already giving Apache all the information it needs, though (with ServerAlias directives)... But if spelling-out the

Re: [users@httpd] SNI with apache 2.4.1 reverse proxy

2012-04-16 Thread Michael Weiser
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