Not able to unsecure pages [#841274]

I moved from one hosting provider to another, installed SSL and suddenly all pages are secured and not just the ones that are listed to be secured.

Question: Does it make a difference if the SSL is for www.mydomain.com instead of mydomain.com ?

At this moment I can't save any changes in the site content or admin settings - every time I hit save, a message pops up that the connection is partially encrypted and if I'm OK with that. When I hit continue, the page refreshes but without saving any changes.

Anyone a brilliant idea how to solve this?

Thanks,
Marty

Comments

Comment #1

marty77 commented 30 June 2010 at 10:56

Title:

All pages are secured

» Not able to unsecure pages

Comment #2

marty77 commented 30 June 2010 at 16:10

Ok - I know a bit more about the problem now.

If secure pages is enabled, I can't do any changes in the content or admin settings. The message that pops up is:

"Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party. Are you sure you want to continue sending this information?"

When I hit continue, the page just refreshes without saving changes.

So I disabled the module in the database and all is fine again (except that the complete site is SSL instead of a few pages...).

I removed and reinstalled secure pages again, but the same error message pops up when the module is enabled and again, changes cannot be saved.

I thought this might had something to do with the site change, as I wrote in the first post, but along with moving the site to another hoster, I updated to drupal 6.17 - perhaps secure pages is not compatible with 6.17 ?

Does anyone have an idea how to solve this?

Marty

Comment #3

jpdaut commented 25 July 2010 at 20:29

I have exactly the same problem.

marty77 have you been able to learn more about this problem?

Comment #4

jasont28 commented 29 July 2010 at 02:36

I have Drupal 6.16 and am experiencing the same problem so I don't believe it is a problem with Core. For me, I saved the Secure Pages configuration today after adding imce/* to the ignore pages list. Now, the rules I have set for Secure Pages don't seem to be followed. The home page for anonymous users is being redirected to https when it is not included in the "Make secure only the listed pages" list. When logged in as a user, the home page is reverted back to http.

It seems somewhat random though I know these problems never are. Some public pages are coming up in https for anonymous visitors whilst other public pages are coming up as http. This is a serious problem.