Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All service: Internal Server Error due to prosEO Messages #200

Open
katharinabassler opened this issue Sep 28, 2023 · 0 comments
Open

All service: Internal Server Error due to prosEO Messages #200

katharinabassler opened this issue Sep 28, 2023 · 0 comments
Assignees
Labels
bug Something isn't working implemented Issue has been implemented and is ready for test

Comments

@katharinabassler
Copy link
Collaborator

In some instances, a request will return HTTP 500 Internal Server Error even though returning a proper error with a proper message would be possible. The reason is that some prosEO messages contain line breaks, e.g. due to stack traces, which causes the return of a malformed HTTP response, which in turn is interpreted as an internal server error.

An example is given below:

{
"timestamp": "2023-08-25T09:17:19.059+0000",
"status": 500,
"error": "Internal Server Error",
"message": "Invalid characters (CR/LF) in header Warning",
"path": "/proseo/notification/v0.1/notify"
}

@katharinabassler katharinabassler added the bug Something isn't working label Sep 28, 2023
@emelchinger emelchinger added the implemented Issue has been implemented and is ready for test label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working implemented Issue has been implemented and is ready for test
Projects
None yet
Development

No branches or pull requests

3 participants