4 ms·
If you're trying to figure out CORS errors, it means you're either loading fonts or making XMLHttpRequests across domains. Neither of those were available in th
by jakelazaroff 5y ago
If you're trying to figure out CORS errors, it means you're either loading fonts or making XMLHttpRequests across domains. Neither of those were available in the 90s era OP is rhapsodizing about. You don't have to use the additional features/complexity of the past 15–20 years… but if you do, it's not surprising that things get a little more complex!
- la_fayette 5y agoIE had ActiveX since 1996, which allowed for things similar to Ajax.
- saulpw 5y agoYou actually do have to use HTTPS nowadays, and that's a non-trivial amount of complexity compared to just serving up a static page over HTTP.
- inkeddeveloper 5y agoNo it’s not. Certs are pretty dumbed down. So much so that there is a thing called certbot that just does it for you.
- saulpw 5y agoYeah, we run certbot. It fails for some reason at least once a year and we have to do something to fix it. At the very least you have to find a way to run it on the regular and you can't forget about it or else your simple static website starts looking like malware. Tell me again how trivial it is for a 15-year-old kid using their parents' Windows 10 machine to get certbot running reliably.
- hrisng 5y agoEh, most static site hosting provider offer it out of the box nowadays