Custom error is very useful for customizing the error pages, but shouldn't the error page be sent with the original response code (i.e. 403 or 404) instead of 200, which it currently sends?

By sending an HTTP 200 code, the search engines will still think its a valid page, and will index a customized error page for an incorrect URL.

Comments

kbahey’s picture

kbahey commented

Yes.

Do you have a patch that fixes this?

subdian’s picture

subdian commented

I'm afraid I don't. But I would sure like one :-)

I could take a look... I'd imagine it can't be that difficult

kbahey’s picture

kbahey commented
Version: 5.x-1.1 » 6.x-1.x-dev
Status: Active » Fixed

I put in a fix for the 5.x-1.x-dev and 6.x-1.x-dev versions of the module.

It should be available in about 9 hours in the tarball.

Please test that version tomorrow.

toemaz’s picture

toemaz commented

Tested with the dev release for D5 and confirms that it works fine. Perhaps you can make a new release?

kbahey’s picture

kbahey commented

New stable releases created for 5.x and 6.x.

Should appear shortly on the project page.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 49aca8a on 6.x-1.x, 8.x-1.x by kbahey: 
    #405822 Was not sending 403/404 HTTP code in the headers