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

Misleading log message when service does not exists #99

Open
pehala opened this issue Dec 14, 2022 · 0 comments
Open

Misleading log message when service does not exists #99

pehala opened this issue Dec 14, 2022 · 0 comments

Comments

@pehala
Copy link
Collaborator

pehala commented Dec 14, 2022

If you specify a service that doesn't exists, the WASM will report it like this:
2022-12-14T11:49:33.745044Z error envoy wasm wasm log: (root/2) 2078290764: failed to initiate fetch of configuration data for 65: failed to dispatch HTTP (https) call to cluster outbound|443||<authority> with authority <authority>: BadArgument
The actual system endpoint will return 404 and not 400 as would the error message suggest.

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

1 participant