HTTP to HTTPS and Back

The only benefit of using "starts_with" over "contains" is to check whether the uri is at the start of the request. There is no significant performance improvement from one to the other.If you use the contains, then all of these requests would match

 

 

http://server/getting_started/contact.asp

 

http://server/some_path/getting_started/contact.asp

 

http://server/some_other_path/page.html?foo=/getting_started/contact.asp

 

 

Not that this is likely to happen, but it's an option. To be the safest, you should put all known paths in your secure_uri's class and use the starts_with operator. But, if you aren't concerned with rogue uri's circumventing your logic, then the contains should work just fine.

 

 

With regards to performance on the rule itself. You are probably better off with two rules so you don't have the overhead of the check on the server port in each request. But, that overhead is fairly negligible so you should pick the option that is most maintainable for you.

 

 

-Joe