Escaped error message with regex validation

[kesla]

Similarly to #1012, the error messages when doing a validation with regex comes back escaped (and somewhat unreadable).

example:

{
    statusCode: 400,
    error: "Bad Request",
    message: "the value of foo must match the regular expression /^\d+$/",
    validation: {
        source: "path",
        keys: [
            "foo"
        ]
    }
}

Can this be improved somehow? Is there a way to set custom error messages (that would fix my use case)?

[dacbd]

If you are still having this problem, in the short term you can use the onPreResponse extension point to edit the body of the response

link to the onPreResponse extension point in the request life cycle: documentation

[kesla]

@danielbarnes Thanks for the tip, I'm using that right

[hueniverse]

The tricky part is to distinguish between insecure strings coming from the server and those coming from the client as bad input. I need to think about it.