Really it doesn’t take much <cflocation url="https://www.#replace(server_name, 'www.', '')#" addtoken="No" />
To answer the question of "Why make CF process requests when the web server can do it?", for cross platform compatibility. What happpens if the app ends up for some reason on a window web server or what ever? Steve -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of michael sharman Sent: Friday, 11 July 2008 9:02 PM To: cfaussie Subject: [cfaussie] Re: [OT] .htaccess You really don't want this at the ColdFusion level because it creates extra load on the application server. Apache can inherently handle a LOT more load than ColdFusion Server, so if you can do it there you really should. Why make CF process requests when the web server can do it? Some say the performance "hit" (when using CF) is negligible, but when the small things start to matter (when traffic increases) trust me...these things make a big difference. Michael On Jul 11, 4:08 pm, "Steve Onnis" <[EMAIL PROTECTED]> wrote: > why dont you just do it with CF? > > _____ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Ricardo Russon > Sent: Friday, 11 July 2008 1:19 PM > To: [email protected] > Subject: [cfaussie] Re: [OT] .htaccess > > Thanks George, > > Im currently using your first suggestion, which gives me everything i > need except for > redirectinghttps://domain.com->https://www.domain.com(as https is > already active) > > Anything I try to do to combine the two seems to create a loop. > > Not that its ultra important, as Kym says I can do it at a script level. > > I would just prefer to have a nice clean solution for this. Doing it > from the .htaccess means that it only gets checked once, doing it a > script level means that it gets checked at every request. > > Ricardo. > > On Fri, Jul 11, 2008 at 12:07 PM, <[EMAIL PROTECTED]> wrote: > > Try the below > > it is checking if https is on and if not it rewrites to the domain u > specify. > > RewriteEngine On > > RewriteCond %{HTTPS} off > > RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} > > If it is using a specified port use the following > > RewriteEngine On > > RewriteCond %{SERVER_PORT} !443 > > RewriteRule (.*)https://www.example.com/require-secure/[R] > > Cheers > > George > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf > > Of Ricardo > Sent: Friday, 11 July 2008 11:10 AM > To: cfaussie > Subject: [cfaussie] [OT] .htaccess > > Can anyone help me with a .htaccess script. > > I need to redirect all traffic that is nothttps://www.domain.comto > > there. > > So... > > http://domain.com > > http://www.domain.com > > https://domain.com > > all need to go to: > > https://www.domain.com > > I can get everything to redirect excepthttps://domain.com > > If anyone has some links that would be great. So far I have turned up > > nothing but some basic examples. Some in depth explanation on how to > > construct these files would be good. > > Thanks, > > Ricardo. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
