X-Staticmap-API-Warning cannot be read through XHR call because of CORS and specific header [110325512]

Assigned

Feature Request

Status Update

No update yet.

Description

be...@groupe-mma.fr

created issue #1

Jun 18, 2018 08:23AM

Issue report
----------------
We want to monitor X-Staticmap-API-Warning. But we did not find any way to read it through a DOM API of the <img> element. Thus, we tried to get the static map image through Javascript XHR with CORS. The HTTP call and response is Ok, but the user-agent filters the X-Staticmap-API-Warning header because it is not declared in a Access-Control-Expose-Headers response header (see

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers).

What steps will reproduce the problem ?
See

https://codepen.io/benjamin-chevillon/pen/eKePPz

Comments

an...@google.com <an...@google.com> #2Jun 22, 2018 11:36AM

Assigned to yu...@google.com.

Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.

yu...@google.com <yu...@google.com> Jul 18, 2018 11:12PM

Reassigned to an...@google.com.

an...@google.com <an...@google.com> Aug 6, 2018 02:57PM

Reassigned to be...@google.com.

be...@google.com <be...@google.com> Dec 18, 2018 09:06AM

Reassigned to yu...@google.com.

yu...@google.com <yu...@google.com> #3Jan 30, 2019 08:44PM

Reassigned to be...@google.com.

I've transitioned from this team. Thanks!

be...@google.com <be...@google.com> Feb 5, 2019 03:14PM

Reassigned to rh...@google.com.

ma...@google.com <ma...@google.com> Jul 30, 2020 07:58AM

Reassigned to gm...@google.com.

[Deleted User] <[Deleted User]> #4Feb 26, 2021 03:33PM

Any update on this?

mi...@gmail.com <mi...@gmail.com> #5Feb 7, 2025 07:53PM

Was there any update on this issue?

Message last modified on Feb 7, 2025 07:55PM