3 ms·

I’ve always setup HTTPS to an alias domain as the first step in any of my projects. I do it because at an early internship I witnessed a bunch of bugs that only

I’ve always setup HTTPS to an alias domain as the first step in any of my projects. I do it because at an early internship I witnessed a bunch of bugs that only appeared after pushing to “prod.” Nowadays with tools like mkcert it’s trivial to install and maintain a trusted root cert for whatever .test (RFC approved TLD) domain you want to add to /etc/hosts. (Just be careful which colleagues you allow to install a custom root cert on your device. ;)) As a fULlStAck DeVeLoPEr, what annoys me the most are the preflight CORS OPTIONS requests, and the fact they came out of nowhere in the past ~5 years. Most frameworks don’t have a good solution for dealing with those requests out of the box. It’s annoying how web standards change so much so frequently. I could put my code in a vault and take it out in 2023 and it would probably break due to some obscure update in whatever JS runtime is popular then.

TheCoelacanth 6y ago
Prior to the introduction of CORS preflight requests, those same requests simply would have been blocked by the browser. Your old code will still work. If you see CORS preflight requests, then you are using new capabilities that didn't exist before CORS.
wereHamster 6y ago
In my current project I use mitmproxy for that. It generates a CA that I can trust via my keychain, and don't have to worry about how to import the mkcert certificates into various servers (rails, nodejs express, next.js etc). It's easy enough to run mitmproxy parallel to the application server.
- pineconewarrior 6y ago
  Do you think this is a good option for Windows -> WSL2 -> docker stuff? I've had trouble with MKCert in these scenarios
pineconewarrior 6y ago
I've had a bit of trouble getting mkcert working properly, but my setup is a bit weird. Windows 10 -> WSL2 -> Docker. It works, but it's a bit finnicky. I've had similar problems with the OPTIONS, particularly in dealing with some rather dated Magento stores.

TheCoelacanth 6y ago

Prior to the introduction of CORS preflight requests, those same requests simply would have been blocked by the browser. Your old code will still work. If you see CORS preflight requests, then you are using new capabilities that didn't exist before CORS.

wereHamster 6y ago

In my current project I use mitmproxy for that. It generates a CA that I can trust via my keychain, and don't have to worry about how to import the mkcert certificates into various servers (rails, nodejs express, next.js etc). It's easy enough to run mitmproxy parallel to the application server.

pineconewarrior 6y ago
Do you think this is a good option for Windows -> WSL2 -> docker stuff? I've had trouble with MKCert in these scenarios

pineconewarrior 6y ago

I've had a bit of trouble getting mkcert working properly, but my setup is a bit weird. Windows 10 -> WSL2 -> Docker. It works, but it's a bit finnicky. I've had similar problems with the OPTIONS, particularly in dealing with some rather dated Magento stores.