Skip to content

Improve error messages in front-end upon server failures #1311

Open
@pcrespov

Description

@pcrespov

Long story short

All 4xx and 5xx errors shall be properly logged (see https://httpstatuses.com/ for details of every) considering the context of the front-end user!

Had a 404 (Not found) upon login in front-end is shown as Error while fetching auth and took me some time to realize that auth was the resource.

Expected behaviour

When webserver responds 404

 "POST /v0/auth/login HTTP/1.1" 404 172 "http://127.0.0.1:8080/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36"

front-end shall log something in the line of "Currently, it is not possible to login [404]" (the latter I would display only if tester (e.g. staging)

Actual behaviour

front-end is shown as Error while fetching auth

Steps to reproduce

  • create config and disable all subsystems
  • start webserver
  • login

Your environment

dev mode

Metadata

Metadata

Assignees

Labels

a:apiframework api, data schemas,a:frontendissue affecting the front-end (area group)t:enhancementImprovement or request on an existing feature

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions