(Not sure if it's already been reported/noticed, but can't really see anything about it so will make an issue just in case.)
It looks like something has recently changed/broken, and now a noembed jsonp request to http:// will redirect through to https:// but with ESI code in place of the callback param, which is then output in the final json.
Hi there,
(Not sure if it's already been reported/noticed, but can't really see anything about it so will make an issue just in case.)
It looks like something has recently changed/broken, and now a noembed jsonp request to http:// will redirect through to https:// but with ESI code in place of the callback param, which is then output in the final json.
Eg. http://noembed.com/embed?callback=something&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2zwhru6VxgQ
will redirect through to https://noembed.com/embed?callback=%3Cesi%3Ainclude%20src%3D%22%2Fesi%2Fjsonp-callback%22%2F%3E&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2zwhru6VxgQ
Which then returns the following jsonp to the browser, which chokes on the
<esi:include
tag:Not sure if it's something on Fastly's end, or if it's anything you have control over.
Switching to just requesting https:// directly seems to fix (eg. https://noembed.com/embed?callback=something&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2zwhru6VxgQ ).
Cheers, Geordie