You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware that StraightMail was designed to stay within its own VPC network (not exposed to the outside), but in a dev environment, it is not uncommon to make the HTTP traffic available to the host, either via:
port forwarding
ngrok-alike tunnel
traefik and Host header routing
path routing
etc...
The current API location (according to swagger UI) is hardcoded:
I'm aware that StraightMail was designed to stay within its own VPC network (not exposed to the outside), but in a dev environment, it is not uncommon to make the HTTP traffic available to the host, either via:
Host
header routingThe current API location (according to swagger UI) is hardcoded:
straightmail/src/main/java/com/encircle360/oss/straightmail/config/ApiConfig.java
Line 17 in 7fa62c9
Perhaps that can be dropped, letting swagger use the current host as server URI?
The text was updated successfully, but these errors were encountered: