Skip to content
This repository has been archived by the owner on Dec 8, 2018. It is now read-only.

UseStatusCodePagesWithReExecute shouldn't pass through the QueryString from the original request #267

Closed
ryanbrandenburg opened this issue Apr 13, 2016 · 2 comments
Assignees
Milestone

Comments

@ryanbrandenburg
Copy link
Contributor

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.

@ryanbrandenburg
Copy link
Contributor Author

CC @Tratcher

@Eilon
Copy link
Member

Eilon commented Apr 14, 2016

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants