Defining port in Custom SSL profile configuration is mandatory
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
When the port is not defined under the <server> tag the default port values(443/80) are not getting set. Therefore we need to mention in the doc that the port is mandatory when defining SSL profiles[1].
Suggested Labels:
type/doc
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked mutual SSL documentation and find the section on configuring dynamic SSL profiles. Check how the tag and port are described, then update the documentation to state that the port is mandatory and verify the wording matches the configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100