[Plugin: WordPress HTTPS (SSL)] HTTPS For WP-ADMIN only, how?

Okay, I have tried the developmental version of the plugin as well, nothing works.

These are the options:
– HTTPS Front Page [Unchecked]
– Force SSL Exclusively [Checked]
– Shared SSL [Unchecked – – since I use a self-signed ssl just to access wp-admin]
– Force Shared SSL Admin [checked and unchecked – – tested both]

what’s not working? Homepage, posts, taxonomy pages, and pages aren’t being redirected from https to http.

Hey Aahan,

This functionality is built-in to WordPress. Please read the FAQ. Let me know if you need anything else.

Edit: Oh, and the option to always force HTTP on your public site would be the “Force SSL Exclusively” option. The next version of the plugin is going to have a much simpler set of options. Most of those options that confuse people should just be on, such as Internal HTTPS Elements, External HTTPS Elements, and Disable Automatic HTTPS. The ByPass External HTTPS Check option is going to be removed entirely.

Thanks,
Mike

Hey Aahan,

For some reason your second post didn’t show up the first time I responded.

I just updated the development version (same link). That should fix the pages not redirecting back to HTTP when the ‘Force SSL Exclusively’ option is enabled.

Thanks,
Mike

okay, I will check it now and report back (in about 30 minutes from now). I am validating my theme at the moment. Thanks for your time Mike.

Hey Mike,

For some reason your second post didn’t show up the first time I responded.

Actually, I couldn’t find my question in the forum when I first posted it. Not until some 30 minutes or so. Automattic folks do some serious-level caching, lol!

This functionality is built-in to WordPress. Please read the FAQ. Let me know if you need anything else.

Actually, I don’t want to force HTTPS on WP-ADMIN, as some plugins (like wp-touch pro) aren’t great with SSL (at least for me they’re broken).

All I want is to force HTTP on the rest, and let WP-ADMIN be accessible via both HTTP and HTTPS.

get me now?

And Your plugin is working great now. It’s redirecting all pages from HTTPS to HTTP, with the exception of WP-ADMIN without any additional config, which is great. (1) That is how it’s supposed to work, right? (2) is it 301 redirecting here right, are you sure? If not is there a way to enable it?

Lastly you’ll continue to support your plugin for the foreseeable future, I hope? (Please, I don’t want to go searching for another plugin when there’s a new wordpress version and your plugin is broken.)

This is the screenshot of my config. which I feel is enough for what I need: https://img1.uploadscreenshot.com/images/orig/8/23913514217-orig.jpg

Hey Aahan,

You don’t need to do anything special to use your admin panel with both HTTP and HTTPS. This works with WordPress even without the plugin.

Using the Force SSL Exclusively option will keep any page or post on your site on HTTP unless you use the Force SSL checkbox for a particular page or post.

Thanks,
Mike

(My full reply wasn’t probably updated by the time you looked at it. Please take a look again.)

You’re both being caught by the spam filter. I’m kicking it.

Hey Aahan,

Yeah, it wasn’t even visible. I just knew you had replied because I got an email about it, haha. Thanks for taking care of the spam filter Ipstenu.

1. Yes, it should only redirect the admin panel to HTTPS if you’re using the force_ssl_admin option in the wp-config.php.
2. Yes, the redirects are 301 redirects. I use the WordPress wp_redirect and send the 301 header when redirecting pages.

I will support this plugin for as long as possible. I don’t plan on stopping any time soon. ??

I really don’t think you have to worry about the plugin ever breaking, though. Most of the functionality is independent of WordPress, so it should work for a long time even if I didn’t update it.

Thanks,
Mike

@ipstenu do you know the reason why our posts are being flagged as spam by the system?

@mvied That relieved me. Thanks. Good day.

It has to do with how often you post and WHAT you post.

If you post a lot in a short time, and use a lot of URLs and code, it gets tripped.