Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iNaturalist API Recommended Practices suggest specifying a user agent header, but it is disallowed by CORS #391

Open
frewsxcv opened this issue Jul 30, 2023 · 0 comments
Labels

Comments

@frewsxcv
Copy link
Contributor

From https://www.inaturalist.org/pages/api+recommended+practices:

If writing software to interact with the API, please consider using a custom User Agent to identify your application, or iNaturalist username, or something we might use to differentiate your requests
The User Agent can be set with an HTTP header, e.g. User-Agent: [[application or user name]

But if you specify this, then clients that honor the Access-Control-Allow-Headers (e.g. Firefox) will not be able to complete the request since User-Agent is not allowed.

Screenshot 2023-07-30 at 12 11 33 AM Screenshot 2023-07-30 at 12 11 18 AM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

2 participants