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 Apr 10, 2018. It is now read-only.
The only thing that might make sense is to be able to override the authenticator for a single request and otherwise using the one in IRestClient. What's the reason why you want to avoid multiple IRestClient instances?
Basically, I have a web server that's talking to a REST API. The web server passes creds on to the API. Managing the RestClient per scope is what I'm doing.
I guess I could make a custom client factory that's static basically then just make tons of RestClient instances.
I usually suggest a IRestClient per base URL, because that's the common usage scenario where you have a base URL and access only paths relative to this base URL. Your use case is quite uncommon, but it's valid. I should create a V4.1 for this.
Would it make more sense to have Authenticator on the RestRequest? I could then reuse clients across different usages of authentication.
The text was updated successfully, but these errors were encountered: