On Tue, 05 May 2009 13:20:56 -0500, Skip Evans wrote:

>But now I have a problem implementing this on their 
>development site, which is just a duplicate code base inside a 
>directory public_html/_dev and a domain name dev.sitename.com, 
>instead of sitename.com.
>The problem is, and I believe it may be the .htaccess file, 
>redirecting the https pages to the live [...]

You should be telling the browser to redirect to the new page, rather
than just pulling up a page to offer back instead of the requested URL.
You want the browser to request a new page, using HTTPS (i.e. SSL or
TLS). See here, which forces a redirect to HTTPS for any pages in the
orders folder that have been requested via HTTP:

RewriteCond %{SERVER_PORT}  !443$
RewriteRule ^orders/?.*$    https://%{SERVER_NAME}/orders [R=301,L]

The bit at the end, R=301 makes Apache tell the browser to ask for
another page at the new URL.

The %{SERVER_NAME} bit tells Apache to insert the server name, whether
it be your sitename.com or dev.sitename.com
Ross McKay, Toronto, NSW Australia
"Let the laddie play wi the knife - he'll learn"
- The Wee Book of Calvin

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to