Add User-Agent to either the RestClient or RestRequest about restsharp HOT 6 CLOSED

I added UserAgent to my fork, but I only added it to the RestClient, not the RestRequest. What would a use-case be for overriding it for a particular request?

from restsharp.

Haven't seen a case for it TBH. I could imagine some test application impersonating different clients/bots, but I think that's a rather small use case. Did you change the _restrictedHeaderActions in Http.cs to throw away the user-agent if set as a Header-parameter? If not, that would give users the option to override it anyway without the need to have an overly visible property on the RestRequest that could confuse people.

Should there be a default User-Agent ("RestSharp 1.x.x.x") or would that be to obnoxious?

from restsharp.

I don't mind a default. I've run into APIs that will reject requests if there isn't one so it's probably good to have a default.

from restsharp.

I added this

from restsharp.

thanks!

from restsharp.

Awesome, Thanks!

from restsharp.