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.
As a past user of woof I was excited to see a maintained version and figured I'd go ahead and add the feature I most wanted and saw was also on the wish list.
Uses the packed-in ssl library and adds four new cli options to control the tls configuration. I took a stab at what those cli options should look like, though I did go back and forth on what the usage page should look like with them. I'm open to feedback on those, as I'm not sure I particularly like what I settled on.
-t to enable TLS mode
--cert to specify the path to a signed certificate
--key to specify the path to the key file
--keypass to provide the decryption key for that key file should it be encrypted
In addition, I added values to the wurfrc spec to allow the user to pass some or all of these options that way.
Lastly, I included logic to change the default url protocol and port to https and 8443 when tls mode is requested via either the config file or the cli, unless a custom port is also provided.
I don't think I've added any new bugs, but I'm the only one who's tested it.