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

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

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 > > ProxyPassRevers

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 > >> virt

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

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

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

Re: server push CGI problem

2002-08-13 Thread Michael Weiser
On Mon, 12 Aug 2002, Justin Erenkrantz wrote: > > I've got an update problem regarding apache 1.3.24/2.0.39 and a home-grown > > server-push webcam CGI. The CGI continuously reads images from the cam, > Can you try 2.0.40 as I believe some of the CGI handling was been > rewritten since .39? > > S

server push CGI problem

2002-08-12 Thread Michael Weiser
Hi, I've got an update problem regarding apache 1.3.24/2.0.39 and a home-grown server-push webcam CGI. The CGI continuously reads images from the cam, compresses them into JPEGs and puts them together into a multipart/x-mixed-replace stream to produce a poor-man's video with netscape-browsers. W