Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
Dave ReidDoes the 'about' page on your Drupal site actually exist yet?
Comment #2
seanrOf 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).
Comment #3
Dave ReidIs it a Drupal 404 page that you see or a server-type 404 page?
Comment #4
seanrDrupal 404.
Comment #5
yuriy.babenko CreditAttribution: yuriy.babenko commentedAlso 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.
Comment #6
yuriy.babenko CreditAttribution: yuriy.babenko commented