On Fri, Sep 23, 2011 at 6:40 AM, robert.aeschlim...@swisscom.com wrote:
On 09/22/2011 02:12, Eric Covener wrote:
On Wed, Sep 21, 2011 at 6:32 PM, morteemortee.li...@kavemalna.hu wrote:
Any ideas about this topic?
Can't do it.
Why is it sooo really impossible? It can recognise a plain
Nobody has spent their time implementing such a thing, so you cannot do it.
On Sep 22, 2011 11:02 PM, mortee mortee.li...@kavemalna.hu wrote:
On 09/22/2011 02:12, Eric Covener wrote:
On Wed, Sep 21, 2011 at 6:32 PM, morteemortee.li...@kavemalna.hu
wrote:
Any ideas about this topic?
On 9/21/2011 5:32 PM, mortee wrote:
Any ideas about this topic?
On 09/08/2011 11:41, mortee wrote:
Hello,
Is there a way to enable both SSLEngine and plain HTTP forward proxying
on the same port / virtual host?
To be specific, I want my Apache to serve usual HTTPS on port 443, but
On 09/22/2011 02:12, Eric Covener wrote:
On Wed, Sep 21, 2011 at 6:32 PM, morteemortee.li...@kavemalna.hu wrote:
Any ideas about this topic?
Can't do it.
Why is it sooo really impossible? It can recognise a plain HTTP request
attempt on the SSL port, and it can return a reasonable error
Gesendet mit meinem HTC
- Reply message -
Von: mortee mortee.li...@kavemalna.hu
An: users@httpd.apache.org users@httpd.apache.org
Betreff: [users@httpd] Re: mod_proxy SSL forward proxy
Datum: Fr., Sep. 23, 2011 05:02
On 09/22/2011 02:12, Eric Covener wrote:
On Wed, Sep 21, 2011 at 6
Any ideas about this topic?
On 09/08/2011 11:41, mortee wrote:
Hello,
Is there a way to enable both SSLEngine and plain HTTP forward proxying
on the same port / virtual host?
To be specific, I want my Apache to serve usual HTTPS on port 443, but
also act as a proxy server using the
On Wed, Sep 21, 2011 at 6:32 PM, mortee mortee.li...@kavemalna.hu wrote:
Any ideas about this topic?
Can't do it.
-
The official User-To-User support forum of the Apache HTTP Server Project.
See
Hello,
Is there a way to enable both SSLEngine and plain HTTP forward proxying
on the same port / virtual host?
To be specific, I want my Apache to serve usual HTTPS on port 443, but
also act as a proxy server using the ProxyRequests directive on the same
port. That's because I don't have