StripPrefix middleware behavior with chained request transformations

Traefik utilizes a dynamic configuration system where middleware can be chained to manipulate requests before they reach a backend service. A common requirement involves using the StripPrefix middleware to remove specific URL segments to ensure the backend receives a path it recognizes.

When combining StripPrefix with other request-altering middlewares—such as those adding custom headers or performing authentication—the sequence of execution determines the final request structure. There is uncertainty regarding how the internal request state is handled when multiple prefix-altering middlewares are applied in a single chain.

• Does the order of middleware execution affect the ability of subsequent middlewares to match paths based on the original URL?
• How does Traefik handle the request path if multiple StripPrefix middlewares are applied sequentially to the same request?