The proxy configuration is currently set up to only redirect requests that exactly match the specified paths in the configuration. Any other requests that do not match are attempted to be resolved locally.
For example:
• A request to /test is redirected through the proxy according to the configuration.
• A request to /test/file.js, however, does not match the exact configuration and is therefore resolved locally rather than being sent through the proxy.
Ideally, the proxy should be configured to handle more complex routing rules. It should be capable of redirecting not just exact matches but also any sub-paths or related files associated with the specified path. For instance:
• Both /test and any sub-paths like /test/file.js should be redirected through the proxy, ensuring that all relevant resources are handled consistently.
This would provide more comprehensive coverage and ensure that all related resources are properly managed by the proxy, preventing any unexpected local resolution of requests.
The proxy configuration is currently set up to only redirect requests that exactly match the specified paths in the configuration. Any other requests that do not match are attempted to be resolved locally.
For example:
Ideally, the proxy should be configured to handle more complex routing rules. It should be capable of redirecting not just exact matches but also any sub-paths or related files associated with the specified path. For instance:
This would provide more comprehensive coverage and ensure that all related resources are properly managed by the proxy, preventing any unexpected local resolution of requests.