Fix NullPointerException when disabling and reenabling SSL #1027
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.
Setting
keyStore
tonull
will result inNullPointerException
when SSL is reenabled andloadKeyStoreAndCreateCertificate
is executed. Load a null key store instead.Avoid adding
strict-transport-security
header twice. The second addition ofstrict-transport-security
header does not check whether fproxy SSL is enabled becausecontainer
is not a static member. As a result,strict-transport-security
header is sent when SSL is enabled but fproxy SSL is disabled.