I performed some dummy-testing to see whether navigational errors are handled correctly? Here I report my findings:

1. Case A: extra chars at the end
First I accidentally typed this: https://localize-7.staging.devdrupal.org/translate/languages/hu/t
Not a 404 error (as expected), but the regular team page appears. Although almost correctly: 2 blocks are missing (see screenshot attached). Counter-tested against live localize.drupal.org: same working found.

2. Case B: missing chars
Wrong URL (https://localize-7.staging.devdrupal.org/translate/languages/h) returns a white screen. Counter-tested against live localize.drupal.org: returns proper "Page not found message"

CommentFileSizeAuthor
Kep.png245.43 KBBalu Ertl
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

SebCorbin’s picture

SebCorbin CreditAttribution: SebCorbin at Makina Corpus commented

Case A is typical form Drupal route solver.

Case B should return a 404 not found though.