Missing information in documentation about SNI

Open Beginner friendly
#5,430 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Start with the version 2.40 documentation section 5.9.2, “Server Name Indication (SNI) Support,” and verify the statement about setting the Host header with the HttpUrlConnector provider. Update that section to mention the required sun.net.http.allowRestrictedHeaders property; done means the prerequisite is clearly documented alongside the existing guidance.

Written by the indexing model from the issue text.

Description

In documentation for version 2.40, section 5.9.2. Server Name Indication (SNI) Support it is said
"There might be use-cases where the SNIHostName is required to be set for other host than the host specified in the HTTPS request. For those cases, when the HTTP header Host is set, the SNIHostName is set for the host specified in the Host header"

When one sets the Host header with the HttpUrlConnector provider, the property sun.net.http.allowRestrictedHeaders must also be set to true.

Dominant language
Java
Stars
730
Forks
382
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-ee4j/jersey

All issues in eclipse-ee4j/jersey

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.