Causing problems with force_ssl_admin

So, to clarify: normal pages work fine, but the admin pages cause a redirect when using https via FORCE_SSL_ADMIN and eme?

hmmm, not sure if I understand you, let me try again.

I am using wordpress https to secure certain pages, that works ok.

But when I want to secure the admin along with these pages( by using force_ssl_admin or by checking the box in the WPhtts plugin to force ssl admin), I get infinite refreshes on all of the pages that were to be delivered normally (all http pages).

The https pages and the admin are correctly served as https, and with no refresh loop.

Does that make sense?

I just need to understand the test scenario I need to reproduce ??
I’ll try something this evening.

Thank you so very much!

I just tested with
define('FORCE_SSL_ADMIN', true);
in wp-config.php on localhost: all works well, http and https, even multisites. So I think you need to use something like firebug (to debug network traffic when using firefox) to see what url causes the redirection.
Also: check the value of “home” and “siteurl” in the wp_options table to make sure those are correct.

Thank you for reviewing this. Just to check, I have wp installed in a subdirectory of the root, and both home and siteurl are defined to that subdirectory – is this the correct setup for the ssl to work?

Using firebug network, I do not see the redirects, so it has been hard to track. All I do know, is that disabling eme makes the site work properly.

Is there anything else I could look for? I will go over these again to make sure I havent missed anything.

In my test setup, both home and siteurl are set to:
https://localhost/wordpress

Sp maybe ssl isn’t the cause at all, but maybe some rewrite rules?
If you say that you see infinite redirects, you should see that with firebug as well, no?
Can you provide a test setup where this behaviour happens, so I can check?
You can mail me the url at liedekef [at] telenet.be ; I’ll take a look at it tomorrow (1am here now)

Finally! I was able to replicate this error on a new test site. I sent you the info just now.

I think the problem is related by the wordpress ajax method, the EME setting “use client clock” and the forced use of https in the admin backend: based on the code found in https://www.garyc40.com/2010/03/5-tips-for-using-ajax-in-wordpress/, I use admin_url to get the admin-ajax.php url (to learn the client time EME uses ajax), but since this might be https and the rest not, the generated php session id is not valid.
So please try if this change fixes it:

https://plugins.trac.www.ads-software.com/changeset/750528

Yes yes yes yes !!

I just updated it on 3 different sites and all are working! Thank you so very very much – I spent a month debugging this and always ended up in the admin-ajax area, but I didnt know enough to know where to go next.

I’ll let you know if I see any further problems, but for what I see now, this fixed the problem

Thanks again!!

Have a great weekend!

Glad to hear it works, it will be in the next version.