Document user-agent headers for browsers (Safari, Chrome, Mozilla)

[victorosorioparis]

What

• Currently it is not possible to set User-Agent headers in both Chrome and Safari, which are the most important browsers nowadays.

Your API documentation requires that this part of the request header is set with some user informations, I guess for statics purposes and to avoid abuse, warning that if not used the calls from the origin address will be blocked.

Since this is not possible, it would be a good idea to use another field or method from the request to put this information.

Sorry if there is another request like this, I could not found it.

Part of

• API (Tracker) #5523

[stephanegigandet]

One way could be to pass ?user_agent=your app in the URL.

[ocervell]

Just tested a request on Chrome, it actually sets a user-agent:

user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36

Not sure about FF but it should be the same behavior.

[eeschiavo]

I'm trying to scan some product and request info from your server adding user-agent as described in docs but this is not allowed, I got CORS errors:

Request header field User-Agent is not allowed by Access-Control-Allow-Headers.

Would be ok to pass this info in the URL as suggested before?

One way could be to pass ?user_agent=your app in the URL.

Thanks

[github-actions]

This issue has been open 90 days with no activity. Can you give it a little love by linking it to a parent issue, adding relevant labels and projets, creating a mockup if applicable, adding code pointers from https://github.com/openfoodfacts/openfoodfacts-server/blob/main/.github/labeler.yml, giving it a priority, editing the original issue to have a more comprehensive description… Thank you very much for your contribution to 🍊 Open Food Facts