"X-content-type-options" header missing from Reverse API response #3241
-
I have noticed an possible issue with using the Nominatim API, specifically the "reverse" endpoint. I am using the latest version of the Python API (https://nominatim.openstreetmap.org/reverse?lat=&lon=&). My app is under local development, but I am making the request using the Fetch API, and am using Microsoft Edge Developer Tools |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The API doesn't serve any executable MIME types (e.g. javascript) so the security treat that a browser accidentially upgrades a non-executable as execuatable isn't given I think. I assume your Microsoft Edge Developer Tools only prints a notification or warning but the fetch request still works? |
Beta Was this translation helpful? Give feedback.
-
Ah, thank you for clarifying that for me! Edge dev tools marks this as an "Error", but you are right in that the fetch request is successful. |
Beta Was this translation helpful? Give feedback.
The API doesn't serve any executable MIME types (e.g. javascript) so the security treat that a browser accidentially upgrades a non-executable as execuatable isn't given I think. I assume your Microsoft Edge Developer Tools only prints a notification or warning but the fetch request still works?
https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md#determining-whether-a-response-is-corb_protected