Hostname verification is governed by two different configs
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
When we want to disable the hostname verification, according to the document [1] we have to disable the [httpClients].verifyHostName property.
However, keyValidation client's and backend client's hostname verification is governed by two different configs. The following doc [1] needs to modify as follows. (we have to add the [httpClients.sslConfig])
[1] https://mg.docs.wso2.com/en/latest/reference/configurations/micro-gw.conf/
[httpClients.sslConfig]
verifyHostName = false
[httpClients]
verifyHostName = false
Note:
According to the requirement, need to use one config instead of maintaining both.
for KeyValidation Client --> httpClients.sslConfig
for Backend Client --> httpClients
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 micro-gw.conf configuration reference and compare the documented [httpClients] setting with the [httpClients.sslConfig] setting described in the issue. Clarify which client each setting governs and update the reference so the hostname-verification behavior and the intended single-configuration requirement are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100