Add SSL option for clients to allow non-standard port options #90
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.
This Pull Request allows a user to configure the option
ssl
to enforce use of SSL or no SSL within the tunnelIt was made in such a way that the default of
null
will retain the current logic that expose uses which isport === 443
It is useful if you want to host expose on something other than port 443 while still using SSL.
Something else that could be added is warning a user if they use
'ssl' => false, 'port' => 443
as most browsers will reject thisMy git skills failed me on #89 so I recreated the commits.