Implementation of 410 unclear

[simonrl]

Hi,

first of all, thanks for sharing this module.

I noticed that there are some mentions of 410 responses in the code, and there's an own branch for it.
However, in version 1.2.4 and 1.2.3, I can't seem to find an option how to set a 410 response to a 404 URL.
Is this implementation complete?

If not, if there are open tasks, I'd be happy to finish this feature because we need it to work. Just tell me what's missing please.

Thanks
Simon

[endercenter]

Hi,
i had the same problem and started working on it to implement this feature.
Until I came across this implementation at the very end.

Its in Observer/Controller/ActionPredispatch.php on Line 165 - 168

if($url=='410'){
$result = $this->resultFactory->create(\Magento\Framework\Controller\ResultFactory::TYPE_FORWARD);
return $result->setModule('experius_pagenotfound')->setController('response')->forward('gone');
}

You have to set the redirect URL to 410 for it to work.

hope this helps some of you even if this report is 2 years old now.

[simonrl]

Nice find.
However, so we're first sending a 301/302 response, and then a 410? Sounds "dirty" to me.

[endercenter]

As far as i can tell its just the one 410 that gets send.
It returns out of the redirect function at Line 167

return $result->setModule('experius_pagenotfound')->setController('response')->forward('gone');

The 301/302 redirect part comes later in this function and should not be reached on 410.
Also the Chrome DevTools only show a single 410 header.
So if i did not miss something it seams ok to me.