This repository has been archived by the owner on Jul 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 610
ReRequest fails on RequestUri changes #519
Labels
Comments
Went ahead and patched it like so: In ResponseHandler.cs, before user callback invocation, save the request uri:
In ResponseHandler.cs, when handling ReRequest, raise a new connection if necessary:
Seems to be working fine for my requirements... |
nirdil
changed the title
ReRequest fails on double attempt
ReRequest fails on RequestUri changes
Nov 13, 2018
Thanks I will take a look when I get time |
justcoding121
added a commit
that referenced
this issue
Nov 20, 2018
Should be fixed in latest beta. |
Looking good, thanks |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I need to automatically follow redirect responses internally and return just the final response.
So I did something like this:
But apparently ReRequest only allows sending the request over an existing server connection, so changing the request uri and requesting a ReRequest does not work.
Here's the relevant responseHandler's code:
The text was updated successfully, but these errors were encountered: