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

Any path component should be accepted #119

Open
linuskendall opened this issue Sep 14, 2021 · 1 comment
Open

Any path component should be accepted #119

linuskendall opened this issue Sep 14, 2021 · 1 comment

Comments

@linuskendall
Copy link

To follow the behaviour of the solana validator and be as transparent as possible the cache should accept any path "/" component of the URL. I have seen some applications use this in the wild and it is supported by the validator.

There are also special URL paths in the validator that get translated into non RPC requests like "/health".

Currently cacherpc returns 404 on any path a part from "/". We work around it in our proxy by just overwriting the path component to any request we pass to zubr cache.

linuskendall added a commit to rpcpool/cacherpc that referenced this issue Sep 14, 2021
Like the validator allow any path for post requests. Addresses issue bestarch-ae#119.
@Fedor-sa
Copy link
Collaborator

Reproduced with 0.1.27

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

No branches or pull requests

2 participants