Closed wilomgfx closed 4 years ago
Thanks @wilomgfx,
Seems like I've gone a little too far with the security headers. Two weeks ago I added the strict-transport-security: max-age=15768000; includeSubDomains; preload
header to the overview page which is delivered via HTTPS.
The individual examples are delivered via HTTP, but since I've accidentally added includeSubDomains
, the browsers will try to access the examples also via HTTPS.
I've removed the includeSubDomains
for now. Seems like all browsers (I've tested Chrome, Safari, Firefox) updated their HSTS knowledge right away after opening the overview page again.
But this is a good reminder to look into the topic of enabling SSL for all examples.
Can you check if the change also works for you? \ naltatis
Works fine now :) thanks a lot!
Great book BTW, we are about to dive deep into micro frontends at work :)
I'm getting
ERR_SSL_PROTOCOL_ERROR
on chromeVersion 83.0.4103.116 (Official Build) (64-bit)
and on latest firefox
It also does not work on latest safari