I have a weird issue occurring.

I have two content types A and B. Both content types have automated URL alias settings to show up as members/title-of-page

When I create node content type A, the node shows up as secure.
When i create node content type B, the node shows up as insecure.

There is no difference in the URL path and the settings are correct in Secure Pages (i.e. I have members/* set to be secure)

Any idea as to why this would happen?

As a side note, what was happening with the insecure node types was that when it was created it would originally go to node/324 or whatever however on the other node type it would show the URL alias. I installed global redirect and this fixed it hwoever Secure Pages doesnt seem to read the URL alias or something.

I hope that all makes sense.

Comments

jeremymcminn’s picture

jeremymcminn commented

Also I will mention, when I am logged in as User 1 with admin menu, when there are no matches, it does not switch back to non-https. Sometimes it does, sometimes it doesnt.

alan d.’s picture

alan d. commented

I just discovered this on a clients site for a node. I was using:

node/19
node/19/*

I modified this to:

node/19
node/19/*
node-19-alias

And it appeared to resolve the issue for us.

This suggests that the URL alias table is being inconsistently used depending on the current protocol. I have not yet used the Drupal 7 version so I do not know if this effects this version as well.

jeremymcminn’s picture

jeremymcminn commented

Thanks Alan - what an odd issue. Will try this and see if it works for me.

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Active » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks