-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why RestClient must contain a value for BaseUrl #775
Comments
If you can provide a valid use case for not requiring a base url on the client I'll see what I can do. No promises. Also, just to make sure it's clear, this may or may not be possible without heavy changes I haven't looked yet so if it will require a big change than it will most likely not happen for a while if at all. |
A valid use case could be that we are calling multiple APIs where one of them have only one endpoint. There is a workaround of course, but it would be nice if we could just pass single URL instead of splitting that single URL to base URL and relative URL. |
Duplicate of #625 |
This is really inconvenient. Enough so that I am considering just going with HttpClient. |
A valid usecase is that you can have a cookie for a top level domain and have to use the cookie in different subdomains. I want to use restsharp client's cookiecontainer ofc. I ended up changing the baseurl every time instead of just creating requests with different urls as needed. |
I think somesone and me not want to set "BaseUrl" because multi difference url in one site;
The text was updated successfully, but these errors were encountered: