Add advice on user agents?
Specific to packages wrapping APIs.
Adding an user agent. Should that user agent be different for package developers themselves and for CI.
Linked to #478 (value added by a wrapper)
Adding an user agent. Should that user agent be different for package developers themselves and for CI.
This is all very much "in flux". I think use of http2 in particular should translate to a general principle of using the same credentials/agents for CI, but also ensuring everything is redacted via httptest2. For other http systems recommendations would differ. So there seems to currently be a strong dependence of recommendations on http systems, but if we presume a general transition towards http2, then we can also presume a direction of future evolution of our recommendations in this regard.
Thanks! But user agents aren't really confidential info?
- the package should provide a default user agent
- the package should let users override it (?)
- the package might change the user agent based on context (CI, package developers)
Why would that be different when using, say, curl?
https://github.com/EMODnet/EMODnetWFS/pull/125