You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
}
The text was updated successfully, but these errors were encountered:
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"
}
The text was updated successfully, but these errors were encountered: