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
The server serving micropython.org is configured to send a HSTS header. This means all connections are forcibly upgraded to TLS (which in general is a good thing).
However the webrepl doesn't work over HTTPS (#15), therefore the hosted webrepl isn't usable for anyone.
Since the HSTS header doesn't set includeSubdomains it should be possible (depending on the hosting setup) to host the webrepl at e.g. webrepl.micropython.org without HTTPS.
The text was updated successfully, but these errors were encountered:
I'm surprised that after three years this hasn't been changed. Is there a reason that the hosted webrepl can't be configured to not send the HSTS header?
As mentioned by @ulope the hosted version is useless - no one can make use of it, as every modern browser will redirect to https.
The server serving micropython.org is configured to send a HSTS header. This means all connections are forcibly upgraded to TLS (which in general is a good thing).
However the webrepl doesn't work over HTTPS (#15), therefore the hosted webrepl isn't usable for anyone.
Since the HSTS header doesn't set
includeSubdomains
it should be possible (depending on the hosting setup) to host the webrepl at e.g.webrepl.micropython.org
without HTTPS.The text was updated successfully, but these errors were encountered: