Wrong http status code on feed

[sshcli]

Steps to reproduce the issue

1. Try to access to the Welcome Mat Feed ( https://example.com/welcome-mat?format=feed ) it should work ok, you should see the feed

2. Now try to access to the Welcome Mat Feed with a typo in the URL ( https://example.com/welc-mat?format=feed )

Expected result

You should get HTTP status code: 404 Not Found

Actual result

You get HTTP status code: 500 Internal Server Error

System information (as much as possible)

Joomla version: 3.8.6 Kunena version: 5.1.0-RC6-DEV Php version: 7.2.4 Database version: MySQL 5.6.38

Additional comments

[xillibit]

I have tried with your example and i obtain an 404 error

[sshcli]

Please test it with these:

Good URL: https://k51.jobsnear.net/sub-category?format=feed

Bad URL: https://k51.jobsnear.net/subx-category?format=feed

Even if you see a 404 in the page title, the real http status code is 500

You can also test above URLs with this tool: https://httpstatus.io/

[810]

i have changed all 500 to 510, and i still see 500, so i think its from joomla core itself

[sshcli]

Additional comments:

1. The problem is for both, General RSS and Category RSS
2. You start to see these errors in the google dashboard after modify the category alias to an existing category (Because those links are being indexed by google)

[sshcli]

ohh, maybe to take into consideration for k.6 or above: JSON Feed

[pgasiorowski]

I think this ones comes from

Call to undefined method Joomla\CMS\Document\FeedDocument::addHeadLink()

which is a known issue since 3.8.2 https://github.com/joomla/joomla-cms/pull/18966 https://github.com/joomla/joomla-cms/issues/18962

[pgasiorowski]

Other notes:

• It might not a big issue when Kunena is setup for registered users only so Google won't be able to reach the feed URLs
• This might already be fixed when custom template is in use. Otherwise no easy workaround may exist. One possible workaround
  • Create custom Joomla template from Protostar template
  • Edit /templates/[template]/error.php
  • Remove this block: <?php if (JModuleHelper::getModule('mod_search')) : ?>
  • Unless there is a way to create a template override for /templates/protostar/error.php (which I'm unaware of)

[sshcli]

Remove this block: <?php if (JModuleHelper::getModule('mod_search')) : ?>

That one solves this problem, I just tested.

What's next? A. New PR in Joomla B. New PR in Kunena C. Forget about a general fix, keep the changes only for me and close this issue.

[xillibit]

It seems to have no easy fix for that, so keep this for others users which have the same issue

[Sulpher]

I got the same issue after upgrading from 5.0 to Kunena 5.1.3. Joomla 3.8.12 Kunena 5.1.3 PHP 7.0.32

[sshcli]

In the meanwhile, what I'm doing is redirecting all those error pages to a custom 404 page.

Another thing I found is that these URLs are considered dynamic because of the structure example.com/category?format=feed&type=rss

Dynamic URLs are not SEO friendly and we should avoid them when possible

[Sulpher]

Is there any news concerning this issue? Is it possible to fix it?

[sshcli]

what I'm doing is redirecting all those error pages to a custom 404 page.

Redirect 404 pages is not good for SEO

[sshcli]

When Enable RSS Feeds = No You will get 500 internal server errors instead of 404.

You can try it with this url format: example.com/category?format=feed&type=rss

Please let me know if this a different bug not related to this one, to create a new issue for it

Waiting for your response.

[Sulpher]

Finally, I discovered the issue I faced with was caused by 3rd party extension and I got 404 error instead of RSS. Now the problem is resolved. So, my request here was a mistake. As for the issue described in this task, I just been tested with my server environment and could not reproduce 500 error when RSS is enabled or disabled. All works fine on my side.

[pgasiorowski]

I believe this issue has been addressed in recent 3.9.2

[sshcli]

Yes, it has been fixed in J.3.9.2. if Kunena does not need additional changes, we can close this issue.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity.