05-10-2019, 12:15 AM
(05-09-2019, 10:38 AM)Alexandre Machado Wrote: Hi,
after some investigation I'm positive that this is a Chrome bug (or at least an unexpected behavior).
There is nothing wrong with the call or the headers. All other browsers work just fine too.
But more precisely, you can find this thread here, on Chromium bug tracking:
https://bugs.chromium.org/p/chromium/iss...il?id=9891
This is a 10 year old issue which is still open. There are reports from 2009 up to 2018, from people using PHP, ASP.NET, Python, you name it. If you google for "interpreted as Document but transferred with MIME type" you will get around 3K hits. Most developers just ignore it once Chrome devs decided to ignore it as well.
So, in short: there is nothing we can do to avoid this.
Ok. I was thinking i was making something wrong. Thank you Alexandre