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
Description of issue or feature request:
Would it be possible to have a safe way for the user of the update client to customize the Session object used to download files? E.g. providing (limited?) custom parameters for the Session()?
I have two use cases in mind:
provide Authorization credentials (e.g. basic auth or bearer token) that may be needed to access the files
customizing the user-agent header to prepend the application's own <name>/<version>
The text was updated successfully, but these errors were encountered:
I am closing this: both ngclient and the legacy client include a download abstraction that allows any shenanigans a client app might want to do. The included RequestsFetcher implementation does not explicitly expose the requests session but for this purpose a client could easily create their own customized fetcher that modifies the session (this is what I did in my pip POC).
Description of issue or feature request:
Would it be possible to have a safe way for the user of the update client to customize the Session object used to download files? E.g. providing (limited?) custom parameters for the
Session()
?I have two use cases in mind:
<name>/<version>
The text was updated successfully, but these errors were encountered: