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
I've recently tried out --experimental-https option features in the Next CLI documentation. It works great, but I haven't found how I can customise my supported cipher suite. The documentation only seems to support --experimental-https-key, --experimental-https-cert, and --experimental-https-ca as customisation options at the moment.
Alternative solutions
I understand that production environments might deploy a reverse-proxy to act as the TLS terminal. I've also seen valuable comments on using local-ssl-proxy and other third party solutions in this discussion. However, I want to stress that I'm really looking for a solution that can be accomplished within the Next framework itself.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Context
I've recently tried out
--experimental-https
option features in the Next CLI documentation. It works great, but I haven't found how I can customise my supported cipher suite. The documentation only seems to support--experimental-https-key
,--experimental-https-cert
, and--experimental-https-ca
as customisation options at the moment.Alternative solutions
I understand that production environments might deploy a reverse-proxy to act as the TLS terminal. I've also seen valuable comments on using local-ssl-proxy and other third party solutions in this discussion. However, I want to stress that I'm really looking for a solution that can be accomplished within the Next framework itself.
Beta Was this translation helpful? Give feedback.
All reactions