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 Dec 8, 2018. It is now read-only.
This method currently will pass the Query string from the original request to the re-executed request, even though the path has changed. @Eilon and I were thinking that it should probably be cleared and restored at the same time the original path is restored.
The text was updated successfully, but these errors were encountered:
Indeed, using the original query string for the new request seems a tiny bit risky because it could quite likely affect the behavior of the sub-request. Obviously we don't want to clear everything, but if we change the path, we ought to change the rest of the URL, which means changing the query string.
This method currently will pass the Query string from the original request to the re-executed request, even though the path has changed. @Eilon and I were thinking that it should probably be cleared and restored at the same time the original path is restored.
The text was updated successfully, but these errors were encountered: