Issue Feature Under Review Orphaned

#89518Decouple static routes from site config

Daniel Goerz 10/25/19, 18:37 updated 04/22/24, 19:07

Description

Regarding the restrictions of static routes, we tried to find a solution for all use cases but unfortunately this is not possible with the current architecture of static routes. The main design flaw is that static routes are bound to sites but sites do not have to be exclusive in terms of their base. This leads to an arbitrary static route resolving.

To circumvent the current restriction on site configurations that have no dedicated entry point “/” the only solution would be to consider rearranging the Middlewares in your installation.

Goal:

We need to decouple static routes from site configuration and treat them more like redirects are treated now. They need to be globally defined to remove the arbitrariness when resolving. In this case we could think about serving them in a dedicated sysext (like redirects) because then the functionality could be removed completely if not needed (to reduce bloat).

To keep static routes “deployable” they could live in a yaml file instead of the database and probably be editable through a dedicated backend module.

Reviews 3

History 1137

Show 712 earlier messages
  1. Gerrit Code Review pushed patch set 3 for master to change 62380 status New Under Review <span data-processor="relativetime" data-value="2019-11-22T19:56:44+00:00" > 11/22/19, 19:56 </span>

  1. Susanne Moog commented <span data-processor="relativetime" data-value="2023-03-01T17:09:00+00:00" > 03/01/23, 17:09 </span>

    After working on this for a while, we took a step back and looked at the problem as a whole. We decided to not go with a static global routes approach and instead want to provide a solution for global routing in general. Which in turn can then be used to implement independent static routes where necessary.