You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by anoordover <gi...@git.apache.org> on 2016/06/22 19:13:11 UTC

[GitHub] camel pull request #1048: CAMEL-9638: Introduced SNIHostName config in sslCo...

GitHub user anoordover opened a pull request:

    https://github.com/apache/camel/pull/1048

    CAMEL-9638: Introduced SNIHostName config in sslContextParameters

    Introduced SNIHostName in sslContextParameters.
    Added a test to https://www.mnot.net which throws 403 or 421 when SNIHostName is not used.
    Eventually it might be needed to ignore this test. I didn't find a simple way to test this.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anoordover/camel CAMEL-9638

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1048.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1048
    
----
commit 3d84bbef8879fc7a64c73ad38aae6c20099f1d73
Author: Arno Noordover <an...@users.noreply.github.com>
Date:   2016-06-22T19:07:20Z

    CAMEL-9638: Introduced SNIHostName config in sslContextParameters

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1048: CAMEL-9638: Introduced SNIHostName config in sslCo...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/1048


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---