4 ms·
Please see the section about untrusted headers - this is not fixed by HTTP/2. You're right that being able to point your browser right at the app is very conve
by agwa 5mo ago
Please see the section about untrusted headers - this is not fixed by HTTP/2.
You're right that being able to point your browser right at the app is very convenient. With Go, you can have a command line flag that switches between http.Serve (for development) and fcgi.Serve (for production).
- enneff 5mo agoIn my experience having different serving paths for dev vs production is a recipe for annoying issues. I try to make dev as similar to prod as possible. I’m not sure, I don’t dismiss fcgi outright here, I find the arguments for it compelling (not a huge fan of http for many reasons) but it has to be really worth it to break the consistency of using http everywhere.
- agwa 5mo agoIf you want your dev environment to be as similar to prod as possible, and you use a proxy in prod, then you should use a proxy in dev also. I was presenting a solution to someone who doesn't want to do that.
- enneff 5mo agoI think perhaps I was unclear. I don’t mean the entire dev environment should mirror prod (although it’s great if you can do this for end to end testing). I just mean it’s desirable if the process you’re working on operates the same way in dev as in prod.