[wp-hackers] From SSL to non-SSL

mccormicky mccormicky at gmail.com
Fri Dec 4 17:49:47 UTC 2009

Ok, I added a 3rd site to my test.
Came up the same results as #2.
The case#1 is the exception.
The other 2 site's  themes and textwidgets were edited so that *all
linkage*would use relative paths. This was overkill as it happens.
Seems that as long as all css and js files in the header and all images in
the page are sent with https I can use full paths for navigation and the
browser doesn't object.

So case #1 must have something in *httpd*.*conf*  (?) because I don't see
anything special in .htaccess.
Guess it's a host issue at this point?

On Fri, Dec 4, 2009 at 12:08 PM, mccormicky <mccormicky at gmail.com> wrote:

> Hey thanks for answering despite my newbie double post. Wasn't sure if it
> got sent. Sorry about that.
> The reason I used the plugin http for wordpress isn't because I don't want
> to just redirect the page with Apache
> but that everything called by other wp plugins,js files,css files in
> header.php by wp-head must be using https for the security certificate to
> kick in
>  without an error message: "this page contains insecure items".
> The plugin accomplishes that for me despite having to edit some of the
> other plugins and paste relative paths to the files that aren't made https.
> The plugin can cover most but not all. But its still a lot less work with
> it than without it.
> My post was more to do with redirecting out of ssl than redirecting to ssl
> because I'm doing that ok(well,maybe not if I shouldn't be using wp to do it
> all).
> Just can't seem to get out of ssl if another link in the nav is clicked on
> this one site.
>  I'll add in a 3rd case study and see what happens with it.
> If I have the same results with #3 I guess I'll know the successful site is
> the exception, not the rule.
> On Fri, Dec 4, 2009 at 11:52 AM, Eric Marden <wp at xentek.net> wrote:
>> I think you'd be better off using Apache to redirect the 1 page to SSL and
>> not mess with it on the WP level. If WordPress is not to told to do SSL, it
>> should print out all links as http (full urls) by default and you can let
>> apache see if someone requests the secure page insecurely and 302 Redirect
>> them to the proper link.
>> - Eric Marden
>> __________________________________
>> http://xentek.net/code/wordpress/
>> tw: @xentek
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list