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
For such ESI tag, ETS tries to make a request using http. This is not working for me since my backend server has a redirection from http:// to https://.
There is a sentence in the readme that seems to be an answer, but I expect https:// urls to be requested using HTTPS.
ETS strips Content-Security-Policy headers to enable support for proxying HTTPS origins via HTTP.
The text was updated successfully, but these errors were encountered:
I came across the same issue. ESI includes referenced by https are fetched using http. The origin server have http to https redirect set up. The redirect propagates to the template in which esi tag was inserted and the user is redirected to the url from esi:include src. Furthermore this causes ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION if I use multiple esi:inlcude tags like this.
Using Akamai, I can include a page using HTTPS.
For such ESI tag, ETS tries to make a request using http. This is not working for me since my backend server has a redirection from
http://
tohttps://
.There is a sentence in the readme that seems to be an answer, but I expect
https://
urls to be requested using HTTPS.The text was updated successfully, but these errors were encountered: