You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jamie Johnson <je...@gmail.com> on 2013/03/29 04:21:05 UTC
Proxying SSL Requests on trunk
I am trying to proxy SSL requests to a backend tomcat server using the
latest code on trunk and am having some issues. If I enable
"ProxyPreserveHost" I get a 500 proxy error and investigating the logs I
see that the address being proxied to is the IP address. If I turn off
ProxyPreserveHost the address proxied to is actually the host name (what's
in the ProxyPass definition). Is this expected? I did not expect the
hostname to be resolved to an IP address when doing the proxy with preserve
host on, is this correct? Is there a way to not have the host name
resolved to the IP address?
Re: Proxying SSL Requests on trunk
Posted by Jamie Johnson <je...@gmail.com>.
Ok, I'll move the question to the user list. I figured since this was an
issue I was experiencing with an unreleased version of the software that it
made sense here though.
On Fri, Mar 29, 2013 at 9:35 AM, Eric Covener <co...@gmail.com> wrote:
> On Fri, Mar 29, 2013 at 9:31 AM, Jamie Johnson <je...@gmail.com> wrote:
> > A quick question in regards to this. When enabling ProxyPreserveHost I
> > understand why I'm seeing the mismatch between the hostname and the
> > certificate, but I thought that SSLProxyVerify none and
> SSLProxyCheckPeerCN
> > off would disable the SSL checks associated with proxying, but this was
> not
> > the case. Am I misunderstanding their purpose?
>
> This thread is off-topic for the development list.
>
Re: Proxying SSL Requests on trunk
Posted by Eric Covener <co...@gmail.com>.
On Fri, Mar 29, 2013 at 9:31 AM, Jamie Johnson <je...@gmail.com> wrote:
> A quick question in regards to this. When enabling ProxyPreserveHost I
> understand why I'm seeing the mismatch between the hostname and the
> certificate, but I thought that SSLProxyVerify none and SSLProxyCheckPeerCN
> off would disable the SSL checks associated with proxying, but this was not
> the case. Am I misunderstanding their purpose?
This thread is off-topic for the development list.
Re: Proxying SSL Requests on trunk
Posted by Jamie Johnson <je...@gmail.com>.
A quick question in regards to this. When enabling ProxyPreserveHost I
understand why I'm seeing the mismatch between the hostname and the
certificate, but I thought that SSLProxyVerify none and SSLProxyCheckPeerCN
off would disable the SSL checks associated with proxying, but this was not
the case. Am I misunderstanding their purpose?
On Thu, Mar 28, 2013 at 11:41 PM, Jamie Johnson <je...@gmail.com> wrote:
> Wow, I'm sorry I completely lost sight of the issue here, please ignore
> this, the original request was to the ip address, so this is working
> exactly how it was supposed to. This is what I get for working late at
> night. Again I am sorry.
>
>
> On Thu, Mar 28, 2013 at 11:21 PM, Jamie Johnson <je...@gmail.com> wrote:
>
>> I am trying to proxy SSL requests to a backend tomcat server using the
>> latest code on trunk and am having some issues. If I enable
>> "ProxyPreserveHost" I get a 500 proxy error and investigating the logs I
>> see that the address being proxied to is the IP address. If I turn off
>> ProxyPreserveHost the address proxied to is actually the host name (what's
>> in the ProxyPass definition). Is this expected? I did not expect the
>> hostname to be resolved to an IP address when doing the proxy with preserve
>> host on, is this correct? Is there a way to not have the host name
>> resolved to the IP address?
>>
>
>
Re: Proxying SSL Requests on trunk
Posted by Jamie Johnson <je...@gmail.com>.
Wow, I'm sorry I completely lost sight of the issue here, please ignore
this, the original request was to the ip address, so this is working
exactly how it was supposed to. This is what I get for working late at
night. Again I am sorry.
On Thu, Mar 28, 2013 at 11:21 PM, Jamie Johnson <je...@gmail.com> wrote:
> I am trying to proxy SSL requests to a backend tomcat server using the
> latest code on trunk and am having some issues. If I enable
> "ProxyPreserveHost" I get a 500 proxy error and investigating the logs I
> see that the address being proxied to is the IP address. If I turn off
> ProxyPreserveHost the address proxied to is actually the host name (what's
> in the ProxyPass definition). Is this expected? I did not expect the
> hostname to be resolved to an IP address when doing the proxy with preserve
> host on, is this correct? Is there a way to not have the host name
> resolved to the IP address?
>