Fix naming of disableStrictSSL to disableStrictSsl #487
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently upgraded from 9.3.1 to 12.0.2 and ran into the problem that the request to our swagger couldn't fulfill.
I found out it was because the
--disableStrictSSL
flag didn't work as intended so I debugged a little and could narrow the issue down to the fact that the--disableStrictSSL
arrives asdisableStrictSsl
after processing the args.