We recently launched a new site for a client. Google still has links pointing to example.com/about.html which is now invalid, so we wanted to redirect those with a 301 to example.com/about. I entered about.html in the from field and about (which is an existing path alias) in the to field. Going to about.html should redirect to about, but it does not - I get a 404 instead.

Comments

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)

Does the 'about' page on your Drupal site actually exist yet?

seanr’s picture

Of course. It works if I just go to example.com/about, but the redirect isn't occurring at all - the path shown in the browser's URL bar should still have changed from about.html to about, even if about didn't exist (which it does).

Dave Reid’s picture

Is it a Drupal 404 page that you see or a server-type 404 page?

seanr’s picture

Drupal 404.

yuriy.babenko’s picture

Status: Active » Postponed (maintainer needs more info)

Also experiencing this exact same issue.

/page.shtml set to redirect to /page, but returns a Drupal 404. The /page URL loads fine if requested manually. Interestingly, this functionality works just fine on our dev server, but not on production (same files/database). The only difference is that in the dev environment, the files are directly in /publich_html/ and accessed through domain.com, but in production, the files are in /public_html/new/ and accessed through new.domain.com.

yuriy.babenko’s picture

Status: Postponed (maintainer needs more info) » Active

Status: Postponed (maintainer needs more info) » Active