Skip to content

Cryptic message when a bad filter is passed #3523

Open
@Seluj78

Description

@Seluj78

Description

When calling the API, for example like so:

GET https://shellhub.example.com/api/devices?page=1&per_page=100&filter=W3sidHlwZSI6InByb3BlcnR5IiwicGFyYW1zIjp7Im5hbWUiOiJuYW1lIiwib3BlcmF0b3IiOiJjb250YWlucyIsInZhbHVlIjoidCJ9fV0

We get a 500 (see #3522 for why.)

A 500 isn't a good error message for a bad base64 decode and this message would need to be updated so the end user knows what's wrong

Edition

Community

Version

0.14.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    apiv2Planned for API v2

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions