michael sharman wrote:
> Also if you do want to do it with CF see here:
> 
> http://www.chapter31.com/2007/07/21/detecting-and-redirecting-http-to-https/


I think a few folk have lost the original problem, it is that of 
redirect an unwanted https domain to the wanted one and that is a whole 
different ballgame to going from http to https.

Redirecting at the webserver level is quite viable for straight http, 
for https it is a case of how and when the server decodes the SSL back 
to straight text because until that is done the webserver knows nothing 
about the request. Any rewrite filter has to come after the SSL decode.

As to the performance hit of doing the redirect in the 
application.cfm/cfc page is there not error checking going on there 
anyway? If I was running https that means I want security so I am going 
to be doing a whole bunch of error checks and validation on every 
request. An extra <cfif id hardly going to stop the server dead in its 
tracks. Most frameworks or heavy app coding will take anything up to 
20mS to pass the front end, and extra 0.0somethingSmall is not going to 
make a huge difference.



Just as a matter of interest I wonder as to why the redirect is 
happening for a domain.com to a www.domain.com? Looking at the majority 
of sites here that handle multiple domain names the code in most of them 
strip the "www" off, they do it the other way round (if they care at 
all). They don't redirect per se, they just use the menus so that the 
user gets flicked over at the first link-click anyway.

There is a trend to not use "www" anymore, I might look at a few stats 
so see what the percentage is now.


-- 

Yours,

Kym Kovan
mbcomms


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to