CURLSOAPTransport failure for SP 2.5.2 on CentOS 5.x

[Cantor, Scott]

On 11/6/13, 12:42 AM, "Scott Koranda" <skoranda at gmail.com> wrote:
>
>Another SP 2.5.2 running on CentOS 6.x does not throw this error.

I would be skeptical of that claim, but please reproduce it. That would be
a serious bug, though not as critical as with most software since the
normal behavior is to validate a specific key.

(The reason we don't disable the check is that it ends up confusing
people, and is literally something nobody else would do, so it would just
create interop problems for people. It's easier to just follow standard
https rules as much as possible.)

>How can I configure the SP so that it does not throw an error due to
>the certificate subject name being different than the <VirtualHost>?

There's no normal way to do that for a SOAP call. You can use the
TransportOption hack to override the libcurl setting that does the name
checking by default. It's libcurl doing the check though, not my code, in
the particular case of TLS. I just set the CURLOPT_SSL_VERIFYHOST option
to 2, which does the check.

There are some specific cases other than SOAP where I turn that off.

-- Scott