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
After shipping in Heroku, a hack was added to allow a production build to force HTTPS on the generated URLs that are returned when mapping from the repository to the JSON response. This is because Heroku's load balancers terminate SSL/TLS and hit applications directly using HTTP.
After shipping in Heroku, a hack was added to allow a production build to force HTTPS on the generated URLs that are returned when mapping from the repository to the JSON response. This is because Heroku's load balancers terminate SSL/TLS and hit applications directly using HTTP.
This hack introduced two undesirable changes:
Request
object is directly modified to haveIsHttps = true
.A possible solution is to modify the incoming request using some middleware, possibly after detecting the standard
ASPNETCORE_ENVIRONMENT
variable.The text was updated successfully, but these errors were encountered: