ayseff / securityswitch

Automatically exported from code.google.com/p/securityswitch
Other
2 stars 0 forks source link

Not redirecting to HTTPS when a route is used in path #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Configure with following in web.config (using a route name rather than 
physical file):
  <securitySwitch mode="On">
    <paths>
      <add path="~/checkout" />
    </paths>
  </securitySwitch>
2. Going to /checkout does not do anything.  Changing to the following appears 
to work:
  <securitySwitch mode="On">
    <paths>
      <add path="~/Checkout.aspx" />
    </paths>
  </securitySwitch>
3.

What is the expected output? What do you see instead?
I would expect that I could use routes than than physical paths/file names.

What version of the product are you using? On what operating system?
4.1.4247.0 / Windows Server 2008

Please provide any additional information below.

Original issue reported on code.google.com by meskan...@gmail.com on 29 Sep 2011 at 4:48

GoogleCodeExporter commented 9 years ago
The only problem with URL matching when another module is in play (as is the 
case with Web Forms routing) is .NET cannot guarantee which module will run 
first. So, in this case, the Security Switch module is being executed by .NET 
before the routing module. Therefore, the HttpRequest.RawUrl property is 
returning /Checkout.aspx instead.

I'll look into a possible workaround, but I'm not entirely optimistic that I'll 
find one.

Original comment by vent...@gmail.com on 29 Sep 2011 at 8:04

GoogleCodeExporter commented 9 years ago

Original comment by vent...@gmail.com on 10 Mar 2013 at 1:06

GoogleCodeExporter commented 9 years ago

Original comment by vent...@gmail.com on 24 Aug 2014 at 10:38