Skip to content

Misleading log message when service does not exists #99

@pehala

Description

@pehala

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions