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 Oct 20, 2024. It is now read-only.
We've found a problem whereby if we have an IIS application where WindowsAuthentication is enabled, any redirected URLs do not work.
e.g. if we have a rule whereby /Customers --> /ViewCustomers.aspx, if the user browses to /Customers it keeps prompting for credentials. (If the user browses to /ViewCustomers.aspx it is fine.)
What we've found is that if we change line 142 in RewriterModule such that the call to TransferRequest is just this:
context.Server.TransferRequest(rewrittenUrlPath);
...it works fine. Also if we use the override where JUST preserveForm is set True, it works OK. It seems to be something to do with the method or header arguments being passed, although we're not sure what.
At the moment we're using a modified version of the library with our "fix" in it, but would prefer to keep using your supported version. :-)
The text was updated successfully, but these errors were encountered:
We've found a problem whereby if we have an IIS application where WindowsAuthentication is enabled, any redirected URLs do not work.
e.g. if we have a rule whereby /Customers --> /ViewCustomers.aspx, if the user browses to /Customers it keeps prompting for credentials. (If the user browses to /ViewCustomers.aspx it is fine.)
What we've found is that if we change line 142 in RewriterModule such that the call to TransferRequest is just this:
context.Server.TransferRequest(rewrittenUrlPath);
...it works fine. Also if we use the override where JUST preserveForm is set True, it works OK. It seems to be something to do with the method or header arguments being passed, although we're not sure what.
At the moment we're using a modified version of the library with our "fix" in it, but would prefer to keep using your supported version. :-)
—
Reply to this email directly or view it on GitHub.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've found a problem whereby if we have an IIS application where WindowsAuthentication is enabled, any redirected URLs do not work.
e.g. if we have a rule whereby /Customers --> /ViewCustomers.aspx, if the user browses to /Customers it keeps prompting for credentials. (If the user browses to /ViewCustomers.aspx it is fine.)
What we've found is that if we change line 142 in RewriterModule such that the call to TransferRequest is just this:
context.Server.TransferRequest(rewrittenUrlPath);
...it works fine. Also if we use the override where JUST preserveForm is set True, it works OK. It seems to be something to do with the method or header arguments being passed, although we're not sure what.
At the moment we're using a modified version of the library with our "fix" in it, but would prefer to keep using your supported version. :-)
The text was updated successfully, but these errors were encountered: