0

I have added a redirect via:

Configuration > Search and Metadata > URL Redirects

While accessing the site via SSL. When I add the link the from box auto fills the root of the redirect with https://myRootURL.com/ :

URL Redirects Page

This redirect works for https://myRootURL.com/redirectedLink but does not work for non-ssl: http://myRootURL.com/redirectedLink. I would expect all of these redirects to be ssl/non-ssl agnostic - and the ones auto-generated by Drupal all seem to be.

Is this a configuration issue - or known problem? I have had no luck with Google or browsing the known issues, but I am not sure I am articulating the problem correctly.

EDIT: I am experiencing the same functionality with URL Aliases as well... what configuration options could impact this?

  • The redirect module don't save in database the full URL, only the URIs (source and target, plus language). You can see the infos in the "url_alias" table of your db. So there is no reason this doesn't work with HTTPS, it should be protocol (and domain name) independent. I would suggest to check the HTTPS and Apache conf. – Matt Mar 13 '14 at 16:37
  • That would have been my expectation, but my results are easy to see this is not the case somehow (whether how they are stored or something else) and that it does work for all of the auto-generated redirects. Working on access to the database now. – Matthew Mar 13 '14 at 16:53
0

I am feeling a little sheepish here:

Caching was turned on for anonymous users. When accessing the site as https I was also logged into Drupal, unlike when I was accessing the site over http.

As such the anonymous users were not getting the redirect or alias applied until the cache was cleared. Should have been an obvious first step.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.