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
in ValenceAuthenticator.Authenticate, we overwrite request.Resource with the value from the uri that is computed by RestClient.BuildUri. This means we overwrite any url arg placeholders with their values. So the following code would break:
...
var request = new RestRequest( "/foo/{bar}" );
request.AddUrlSegment( "bar", "123" );
authenticator.Authenticate( request );
// execute request...
request.AddUrlSegment( "bar", "456" ); // won't work: {bar} is gone
authenticator.Authenticate( request );
// execute this new request...
It seems like RestSharp wants to allow this functionality but it is probably uncommon.
The text was updated successfully, but these errors were encountered:
I mean you might send the request and then want to send a duplicate request, but change a url parameter - I think this is technically possible with RestSharp but may not be an intended usage scenario. It certainly seems... unlikely to me.
in ValenceAuthenticator.Authenticate, we overwrite request.Resource with the value from the uri that is computed by RestClient.BuildUri. This means we overwrite any url arg placeholders with their values. So the following code would break:
It seems like RestSharp wants to allow this functionality but it is probably uncommon.
The text was updated successfully, but these errors were encountered: