Problem/Motivation

#2075889: Make Drupal handle incoming paths in a case-insensitive fashion for routing preserved the feature of case sensitive route matching, while making matching case-insensitive in practice when there's no duplicate path.

However there was near-consensus on that issue that examples such as having different pages served by /About and /about on the same site are only theoretical and no-one would ever intentionally use that feature (or that trying to use it would result in many difficulties for users within Drupal and externally).

So we should decide in this issue whether to deprecate the behaviour for 9.x.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

pwolanin’s picture

pwolanin commented

+1 for deprecating it, but feels like that could happen as part of a broader effort to continue to make the routing in Drupal more understandable and streamlined

xjm’s picture

xjm
she/her
Primary language English
commented

We also need to decide how to deal with upstream. From #2075889-352: Make Drupal handle incoming paths in a case-insensitive fashion for routing:

For #348 1-3, I was also struggling with how much to preserve the integrity of the original method, minus what we're overriding. I'm not sure how to handle that problem.

This also reminded me to check whether we ever actually tried to discuss this upstream. In #3 alexpott referenced this previous Symfony PR about it from 2011:
https://github.com/symfony/symfony/pull/297

A few solutions similar to ours, but different, are also proposed at:
http://stackoverflow.com/questions/17538890/how-can-i-make-routing-case-...

And we've done lots of research on this issue that shows that both web clients and the internet generally (in addition to people) do not reliably behave in a case-sensitive way for paths. So I wonder if it's worth reopening the discussion with Symfony six years after the original PR. The original PR was a behavior change, but maybe an API addition to opt in to case-insensitive routing for paths would be considered instead. Because surely we're not the only project to run into this issue (and the comments spanning 5 years on those links also suggest that).

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

Clarified in the summary a little about why we should consider deprecating the case-sensitive matching. I'm not really concerned about people trying to leverage the "feature" intentionally, just people accidentally using it, which is a reason both to preserve the exact match for 8.x for BC, and to deprecate it to mitigate the maintainability burden caused by having it.

Also, it just makes the system harder to understand.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

moshe weitzman’s picture

moshe weitzman commented

Agree that this simplification makes sense.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.