You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2024. It is now read-only.
Today I got an e-mail from Flickr, informing that API calls will have to supply the 'User-Agent' header and there is some discussion raging on https://www.flickr.com/groups/api/discuss/72157721918374433/72157721918403334/. Given that flickrapi uses the requests module, which sends a non-empty User-Agent header by default (even if one supplies the 'headers' parameter), I think we are good here for now.
That said, it would be nice to be able to specify a custom (User-Agent) header (or just a bunch of custom headers in the form of dictionary) when creating the FlickrAPI object.
Or maybe override the default 'User-agent' header with something like flickrapi/3.0.dev0 or such by default.
The text was updated successfully, but these errors were encountered:
Today I got an e-mail from Flickr, informing that API calls will have to supply the 'User-Agent' header and there is some discussion raging on https://www.flickr.com/groups/api/discuss/72157721918374433/72157721918403334/. Given that flickrapi uses the requests module, which sends a non-empty User-Agent header by default (even if one supplies the 'headers' parameter), I think we are good here for now.
That said, it would be nice to be able to specify a custom (User-Agent) header (or just a bunch of custom headers in the form of dictionary) when creating the
FlickrAPI
object.Or maybe override the default 'User-agent' header with something like
flickrapi/3.0.dev0
or such by default.The text was updated successfully, but these errors were encountered: