URL Redirect in HttpModule

[jason859]

Hi,

When I link to our development site with the URL /login.aspx, I get redirected to a webpage.aspx page URL. I eventually end up in the right location, but during the redirect(s) my encrypted data gets changed to lower case which causes the login to fail. Here is an excerpt from an IIS trace log.

<EventData>
<Data Name="ContextId">{00000000-0000-0000-0600-0080000000F5}</Data>
<Data Name="OldUrl">/login.aspx?auth=TQBHAEk...</Data>
<Data Name="NewUrl">/webpage.aspx?webpageid=9&auth=tqbhaek...</Data>
</EventData>
<RenderingInfo Culture="en-US">
<Opcode>URL_CHANGED</Opcode>
</RenderingInfo>

You can see that the auth data (which I truncated above) changes from upper-lower to just lower. I am pretty sure it is AC doing this since the preceding entry in the trace log is for the CommerceBuilder.Services.HttpModule. Why is the rewrite happening? Could it be due to casing differences in the license such as http://www.OurDomain.com versus the browser using http://www.ourdomain.com? The registration used a camel-cased version to set up the license. Note that our production set up is using the same authentication but the redirect isn't occurring. The production license is for a different domain and has the whole domain as lower case.

Additionally, is it correct for the redirect/rewrite being done to change the case of query parameters? I would have never know that a redirect was occurring if it had not been for the change in the case of my auth variable.

Thanks!

[Katie]

Could it be due to casing differences in the license such as http://www.OurDomain.com versus the browser using http://www.ourdomain.com?

If you would like to eliminate this as a possible cause, then feel free to request a new license with all lowercase.

Thanks,
Katie

[jason859]

Hi Katie,

Thanks for the quick response. I may request that they update the licence so at least I could eliminate it as the source of the problem.

In the meantime, I just noticed that my original URL was really /?auth=TQBHAEk... So first there was an additional redirect to /login.aspx to try to authenticate. When I try linking directly to /login.aspx?auth=TQBHAEk... the auth token is left in its original casing. The original link from /?auth=TQBHAEk... doesn't seem to break things on the production server, so something must be different. I also still think that changing the case of the parameters may still be a problem in certain situations, but for my immediate needs, I am now able to work around these issues.

Thanks for your assistance!