Rules for rewriting requests to another path

[Pallavikumarimdb]

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

This PR introduces support for path rewriting rules.

• Middleware creation for different rewrite strategies (exact, prefix, regex, stripPrefix).
• Extended config generation to include path rewrite middlewares in router chains.
• Ensures invalid rewrite configurations are logged and skipped.

This makes it possible to rewrite incoming request paths before forwarding to targets.

How to test?

[Pallavikumarimdb]

Hi @oschwartz10612 , could you please review and let me know if any changes are needed?
@miloschwartz , can you also check if the UI requires any adjustments? Thanks!

[oschwartz10612]

Couple small things:

• I think if we are validating that we require the path to start with a / in the validatePathRewriteConfig we should also enforce that in the API, UI, and Blueprints. Alternatively we could prefix it with a / if it does not have one like on server/routers/traefik/getTraefikConfig.ts:617. I think same thing for stripPrefix
• When using the strip option and leaving the value blank to strip I get [error]: Invalid path rewrite configuration for resource 1: Both rewritePath and rewritePathType must be specified together

As far as I can tell everything else works! We love the UI!

[Pallavikumarimdb]

@oschwartz10612 , I’ve made the requested changes. Could you please review and let me know if any further updates are needed?