Other similar APIs that serve generated CSV files or PDF files of the same data are not effected.
The download is driven by an anchor tag that links to an API which serves the file. The site and the file are served from the same host using HTTPS. Most of their documentation is based around executable downloads so it's not clear how this information effects simple file downloads. Our files and our site meet all the guidelines they lay out.
I have read Chrome's documentation and guidelines about how they determine if something is potentially harmful but it makes no mention of how to resolve issues outside of reaching out to them.
A recent update to Chrome has begun blocking XLSX downloads coming from our website.
0 kommentar(er)
