4 ms·
If (hypothetically at least) the "go service" is running on the device, then if one controls DNS on the device, one can set the A record for the t.co domainname
by 1vuio0pswjnm7 4y ago
If (hypothetically at least) the "go service" is running on the device, then if one controls DNS on the device, one can set the A record for the t.co domainname to the address of the go service. In that case, does one still need a "reverse proxy".
- djhworld 4y agoYeah, I was running the service on a different port though, the proxy was just to work around that.
- 1vuio0pswjnm7 4y agoWhy does service need to run on a different port, i.e., not 80 or 443. What about running the service on the loopback, 127.0.0.2 or whatever. I ask because I have run into similar problems.
- TheHappyOddish 4y agoUsing nginx, caddy, apache etc means you can offload the SSL handling there and let the application just be an application. In the age of containers, setting up a reverse proxy to handle it is minimal effort.
- 1vuio0pswjnm7 4y agoI use forward proxy, not reverse proxy. It requires minimal effort. No containers needed. Not a caddy user, but I believe caddy, with a plugin, can function as a forward proxy.