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
Currently, there doesn't seems to be a straightforward way to toggle between encrypted and unencrypted dev server hosting, short of commenting lines in/out at vite.config.js/ts.
But it seem to me the pain-free solution would be to simply serve both at the same time (by default even?): allow visiting encrypted https:// URLs while preserving their original unencrypted http:// URL variants.
Rationale: recent browsers (in particular: Chrome since half a year ago or so) make it ridiculously hard to specify a whitelist exception to not allowing self-signed/dummy certificates. Making it easier to fallback to unencrypted HTTP when testing such browsers makes dev life a little less painful.
The text was updated successfully, but these errors were encountered:
Handling both http and https would involve two servers and would have to be supported from Vite itself (if the feature is accepted). I don't think there's much we can do from the plugin itself to address this. Maybe you can follow vitejs/vite#16350 which has a similar topic.
Currently, there doesn't seems to be a straightforward way to toggle between encrypted and unencrypted dev server hosting, short of commenting lines in/out at
vite.config.js/ts
.But it seem to me the pain-free solution would be to simply serve both at the same time (by default even?): allow visiting encrypted
https://
URLs while preserving their original unencryptedhttp://
URL variants.Rationale: recent browsers (in particular: Chrome since half a year ago or so) make it ridiculously hard to specify a whitelist exception to not allowing self-signed/dummy certificates. Making it easier to fallback to unencrypted HTTP when testing such browsers makes dev life a little less painful.
The text was updated successfully, but these errors were encountered: