Steps to reproduce
Not sure if this is the right place for this bug but was testing a client/api on Edge 16.16257 and noticed that when getting the headers from the ajax response using
request.getAllResponseHeaders(); would not return any custom headers.
Was working ok in previous versions.
Viewing the link in Chrome Version 60.0.3112.101 once you click ‘Send request’ button in the results can see the custom
XHR exposed response headers: content-type: application/json cache-control: no-cache x-auth: test expires: Mon, 21 Aug 2017 11:33:52 GMT
but when running the same example on Edge 16.16257 get the following result:
XHR exposed response headers: Cache-Control: no-cache Content-Type: application/json Expires: Mon, 21 Aug 2017 11:23:30 GMT
Microsoft EdgeHTML 15.15063
XHR exposed response headers: Cache-Control: no-cache Content-Type: application/json Access-Control-Allow-Origin: http://www.test-cors.org Access-Control-Allow-Credentials: true Access-Control-Expose-Headers: x-auth x-auth: test X-Cloud-Trace-Context: 3fdf25c83c5e5aaa84e8fe49da94d6eb Date: Mon, 21 Aug 2017 11:49:02 GMT Server: Google Frontend Expires: Mon, 21 Aug 2017 11:49:02 GMT Content-Length: 978
Comments and activity
If the link doesn’t work above
- Microsoft Edge Team
Changed Status to “Fixed”
Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 16281 and is available in our latest Insider Preview build in the Fast ring.
The MS Edge Team