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
During deploying a WCF Service to Heroku, it turned out the generated WSDL picks up the port number of the running nginx server for urls, e.g. instead of http://appname.herokuapp.com it was pointing to http://appname.herokuapp.com:1234, where 1234 is the value of the PORT EnvVar.
As the service on $PORT is not available outside Heroku, the WSDL was pointing to unreachable locations.
Heroku Router appends several headers to the request, such as X-Forwarded-Port, which would be the expected port in this case.
Changing fastcgi_param SERVER_PORT $server_port to $http_x_forwarded_port in fastcgi_params fixes this issue (e.g. b26de0c), but I'm not quite sure whether it will have any side effects.
The text was updated successfully, but these errors were encountered:
During deploying a WCF Service to Heroku, it turned out the generated WSDL picks up the port number of the running nginx server for urls, e.g. instead of
http://appname.herokuapp.com
it was pointing tohttp://appname.herokuapp.com:1234
, where 1234 is the value of the PORT EnvVar.As the service on $PORT is not available outside Heroku, the WSDL was pointing to unreachable locations.
Heroku Router appends several headers to the request, such as X-Forwarded-Port, which would be the expected port in this case.
Changing
fastcgi_param SERVER_PORT $server_port
to$http_x_forwarded_port
infastcgi_params
fixes this issue (e.g. b26de0c), but I'm not quite sure whether it will have any side effects.The text was updated successfully, but these errors were encountered: