Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTTP client does not do SNI #21

Closed
2 tasks
hanstrompert opened this issue Oct 18, 2021 · 1 comment
Closed
2 tasks

HTTP client does not do SNI #21

hanstrompert opened this issue Oct 18, 2021 · 1 comment
Labels
bug

Comments

@hanstrompert
Copy link
Member

Description

While using nsi-safnari as part of a nsi-node deployment together with nsi-opennsa and nsi-envoy, it turned out that the HTTP client used in nsi-safnari is not sending a Server Name Indication (SNI) while trying to access nsi-opennsa via nsi-envoy. This was confirmed by examining the nsi-envoy debug logs.

Upgrading this project to a bit more recent version of its dependencies will most likely solve this problem since SNI support is common to almost all recent libraries and frameworks.

Tasks
@hanstrompert hanstrompert mentioned this issue Oct 18, 2021
Closed
1 task
hanstrompert added a commit that referenced this issue Feb 8, 2022
@hanstrompert
working configuration
aa707e5 
- allow all hosts with play.filters.hosts
- configure application secret with play.http.secret.key
- configure key- and truststore with play.ws.ssl
- fix issue #21 HTTP client does not do SNI
- simpler Dockerfile uses release zip from GitHub
- re-added sbt-less to create main.css
@hanstrompert
Copy link
Member Author

Issue is fixed in v2.2.1. The default SSL context generated by the upgraded Play WS library works just fine, including SNI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hanstrompert