0

Regex Rewrites

It would be great if the 'Rewrites' setting supported using regex matching.

 

One example use case is with this regex to redirect Medium articles:

^(?:.*\/)?(?:.*\.medium.com|medium.com\/.*)\/(?:\w+-)+(\w{12})

As users can either have a user page or a subdomain, a regular *.medium.com would not work. Additionally, something like that would also rewrite non-article pages.

 

Currently, for advanced rewrites like this, users are forced to use a browser extension. This is just one example use case, but I'm sure many more exist among power users.

1 reply

null
    • NextDNs
    • yesterday
    • Reported - view

    Your example assumes we can block based on all parts of the URL (i.e. everything after the “/”), which is not possible with DNS blocking.

    Knowing this, your example would be simplified to just “medium.com”, which includes the domain and all its subdomains on our system.

    Similar to custom blocklists, regex is significantly more costly to run than wildcard matching and does not provide the benefits people might expect.

    As we have said many times, for these reasons we are not implementing those features, as we do not believe they would improve our product.

Login to reply

Content aside

  • yesterdayLast active
  • 1Replies
  • 30Views
  • 2 Following