We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We discovered that if you put a trailing slash in the PROXY_ENDPOINT then you'll end up with the TSP dumping ERRO Rejection(NotFound).
ERRO Rejection(NotFound)
This is confusing to the consumer. We should just detect that the trailing slash is present and strip it when they create the client.
Also, we should log the URL that was attempted to be hit when we log a 404 so it's more obvious to see what URL was hit and why it wasn't successful.
The text was updated successfully, but these errors were encountered:
When done with this, create a ticket in the node TSC to do the work there as well.
Sorry, something went wrong.
No branches or pull requests
We discovered that if you put a trailing slash in the PROXY_ENDPOINT then you'll end up with the TSP dumping
ERRO Rejection(NotFound)
.This is confusing to the consumer. We should just detect that the trailing slash is present and strip it when they create the client.
Also, we should log the URL that was attempted to be hit when we log a 404 so it's more obvious to see what URL was hit and why it wasn't successful.
The text was updated successfully, but these errors were encountered: