Skip to content

bug: failed API requests return with mismatched HTTP status code and Content-Type for returned content #317

@TyIsI

Description

@TyIsI

E.g. a failed authentication request returns below:

HTTP/2 200 
server: nginx/1.27.0
date: Mon, 25 Nov 2024 18:37:10 GMT
content-type: application/json
cache-control: no-store, no-cache, must-revalidate
expires: Thu, 19 Nov 1981 08:52:00 GMT
pragma: no-cache
set-cookie: PHPSESSID=ueh3v2t87v042kjefp5jk1outo; path=/
vary: Origin
x-powered-by: PHP/7.4.15
strict-transport-security: max-age=31536000

Incorrect username or password

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Test

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions