Bryan D.

May want to standardize with `wp_make_link_relative()` instead of replacing all occurrences (or limit to first). @GaryJones

So with the proposed implementation you could be also replacing URLs in query string values. So at the very least good idea to limit it to one replacement. Not super...

@GaryJones We can decode the URL's on lookup which will match with how redirects are currently being stored in the posts table (preserving compatibility with existing + new redirects). Following...

You'll also have to be sure to avoid creating additional `cache-control:` headers as one could be set already. These redirects also are cached by their max-age, respecting the TTL, upstream...

@davidsword Thinking this through the default behavior should replace/update the existing redirect. For example, if you used the CLI to "insert-redirect" or "import_from_csv", this would automatically account for any change...

@jeremeylduvall Those pesky trailing slashes never go away :) Thanks for scoping this out and for sharing the provided sample code. I was able to test, validate, and implement automatically...

@GaryJones Do we want to allow the creation of redirects (`$from_url`) for both trailing slash URL variants through the UI? It is currently allowed. This decision impacts how the most...