Currently this module supports only redirect status code 302.
Attached patch makes this configuralbe for the user.
This required changes in the configuration schema to save the redirect lists and status code, so this patch fixes https://www.drupal.org/node/2844613 too.

CommentFileSizeAuthor
#2 redirect-status-2860539.patch3.48 KBChristian.wiedemann
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Christian.wiedemann created an issue. See original summary.

Christian.wiedemann’s picture

Christian.wiedemann CreditAttribution: Christian.wiedemann commented
FileSize
redirect-status-2860539.patch3.48 KB
mlncn’s picture

mlncn CreditAttribution: mlncn as a volunteer and at Agaric for Drutopia, MASS Design Group, Portside commented
Status: Active » Needs review
mlncn’s picture

mlncn CreditAttribution: mlncn as a volunteer and at Agaric for Drutopia, MASS Design Group, Portside commented
Status: Needs review » Needs work

I'm very sorry, after two years of neglect, which is my fault as a maintainer, it needs a re-roll.

That's the good news. The bad news is i'm wondering if we want this redirect functionality in Custom Error at all, or if instead we should drop it and use the now-stable Redirect module for that in Drupal 8?

mlncn’s picture

mlncn CreditAttribution: mlncn as a volunteer and at Agaric for Drutopia, MASS Design Group, Portside commented

Ah, sorry, kbahey made clear in #2822315: Drop support for custom redirects for 404s? that the redirect feature should remain. This still needs a reroll at least though. Thanks.