Change Details

We often have a lot of similarly-structured domain names: - *.wikipedia.org - *.beta.wmflabs.org Each time a new wiki is added, we need to update config.yaml. Especially for quickly changing environments like beta it would be convenient to be able to specify one or more catch-all regexp rules like this: ``` /{domain:/^[^.]+\.beta.wmflabs.org$/}/ ```

We often have a lot of similarly-structured domain names: - *.wikipedia.org - *.beta.wmflabs.org Each time a new wiki is added, we need to update config.yaml. Especially for quickly changing environments like beta it would be convenient to be able to specify one or more catch-all regexp rules like this: ``` /{domain:/^[^.]+\.beta.wmflabs.org$/}/ ``` The regexp match would have a lower precedence than exact matches, but a higher precedence than catch-all patterns (`{domain}`). Disadvantages: - Can't easily enumerate domains configured as a pattern. - Need to rely on backends to properly return error responses when encountering invalid domains fitting the pattern.

We often have a lot of similarly-structured domain names: - *.wikipedia.org - *.beta.wmflabs.org Each time a new wiki is added, we need to update config.yaml. Especially for quickly changing environments like beta it would be convenient to be able to specify one or more catch-all regexp rules like this: ``` /{domain:/^[^.]+\.beta.wmflabs.org$/}/ ``` The regexp match would have a lower precedence than exact matches, but a higher precedence than catch-all patterns (`{domain}`). Disadvantages: - Can't easily enumerate domains configured as a pattern. - Need to rely on backends to properly return error responses when encountering invalid domains fitting the pattern.