You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what problem your feature request solves:
Currently, it is necessary to run the threat dragon application behind a proxy if TLS connectivity is desired.
Describe the solution you'd like:
Since Node and Express natively support TLS, I would like it if variables could be provided in the ENV file to cause the applicaiton to natively accept TLS connections without any proxy being needed.
Hello @ericfitz thanks for taking this on, much appreciated
I have tentatively marked this for the version 2.4 release, due out in April 2025, but there is no pressure: any time you have this ready would be great
Describe what problem your feature request solves:
Currently, it is necessary to run the threat dragon application behind a proxy if TLS connectivity is desired.
Describe the solution you'd like:
Since Node and Express natively support TLS, I would like it if variables could be provided in the ENV file to cause the applicaiton to natively accept TLS connections without any proxy being needed.
Additional context:
I have a fork that has this functionality added:
https://github.com/efitz-oss/threat-dragon
I would like to send a merge request.
The text was updated successfully, but these errors were encountered: