You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a big deal, but looking at logs theres a constant stream of crawlers/bots just recursively looping over these non-existent pages. these pages are surprisingly expensive to generate from a memory standpoint. would be nice to just return a cheap/static "not found" page as well as proper 404 response code.
I also thinks this masks various bugs we have with speaker pages, which would be easier to find if we got a proper error.
The text was updated successfully, but these errors were encountered:
Extra path components (separated by slashes) are ignored if they don't match a more specific menu entry. So if you have a menu entry for path xxx/yyy it'll also receive requests for xxx/yyy/zzz and xxx/yyy/zzz/aaa.
We can add logic either at the server-lever or in the code to redirect these additional params to the canonical but we'd need to do it on a case by case basis.
Sorry to reopen, I just wanted to add a footnote to this issue. Can't do
this easily on Drupal 7, but this is easily achievable in Drupal 8:
https://www.drupal.org/project/force404
Hopefully migration happens by 22x,
Steve
We dont seem to return 404 not found for pages in most case.
Any random string after /speakers, /sponsors/, /blog/, /presentations/, etc results in a page being rendered with content.
For example, I'd expect this to 404 but instead it returns the full list of speakers: http://www.socallinuxexpo.org/scale/13x/speakers/twitter.com/dontrebootme
Similarly https://www.socallinuxexpo.org/blog/this/is/not/a/real/url/ returns the content of /blogs/
Not a big deal, but looking at logs theres a constant stream of crawlers/bots just recursively looping over these non-existent pages. these pages are surprisingly expensive to generate from a memory standpoint. would be nice to just return a cheap/static "not found" page as well as proper 404 response code.
I also thinks this masks various bugs we have with speaker pages, which would be easier to find if we got a proper error.
The text was updated successfully, but these errors were encountered: