Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy path #8

Closed
Az107 opened this issue Aug 4, 2024 · 0 comments · Fixed by #9
Closed

Proxy path #8

Az107 opened this issue Aug 4, 2024 · 0 comments · Fixed by #9
Assignees

Comments

@Az107
Copy link
Owner

Az107 commented Aug 4, 2024

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.

@Az107 Az107 self-assigned this Aug 4, 2024
@Az107 Az107 linked a pull request Aug 4, 2024 that will close this issue
Merged
@Az107 Az107 closed this as completed in #9 Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant