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
{{ message }}
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
It would be very nice if wrangler dev server allows HTTPS access. I think the self-signed certificate is enough.
I maintain Cloudflare Workers to redirect to HTTPS URL on HTTP access on specific pages.
(The website I'm involved is a bit large and I cannot configure that with Page Rules since you can create only 100 Page Rules available.)
I tried to test HTTPS redirection with wrangler dev, but as expected, I opened "http://localhost:8787", then the Worker redirected to "https://localhost:8787" and the error page is shown.
for wrangler dev, we need a way for users to test http vs https. right now localhost server we spin up is always http, and will send https requests upstream to the worker, but that can be confusing behavior ofc. ideally, i'd send the request w/the same protocol that was sent to localhost, but there's the issue of certificates for https localhost.
do https by default, serve wrangler dev locally over https and upstream requests to https, then add an --http flag that is only compatible with bring your own domain configurations that will listen over http and upstream to http
💡 Feature request
Overview and problem statement
It would be very nice if
wrangler dev
server allows HTTPS access. I think the self-signed certificate is enough.I maintain Cloudflare Workers to redirect to HTTPS URL on HTTP access on specific pages.
(The website I'm involved is a bit large and I cannot configure that with Page Rules since you can create only 100 Page Rules available.)
I tried to test HTTPS redirection with
wrangler dev
, but as expected, I opened "http://localhost:8787", then the Worker redirected to "https://localhost:8787" and the error page is shown.@EverlastingBugstopper #1047
The text was updated successfully, but these errors were encountered: