Opened 4 years ago
Last modified 3 years ago
#2452 closed enhancement
petascope - return proper HTTP codes to clients — at Version 1
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 10.0 |
| Component: | petascope | Version: | 9.8 |
| Keywords: | Cc: | ||
| Complexity: | Medium |
Description (last modified by )
503 Service Unavailable (The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded)
→ This should be used when there are no rasservers to process request.
The normal behavior for a client for these particular error codes would be to wait and then re-try the request again, rather than than assuming things just failed and never re-trying again, which in the case of our client would result in a missing tile in the data.
if there is an actual mistake in the script like a syntax error or bad parameters for a function, the server should return a 400 Bad Request error (not a 500).
→ Syntax errors in WCPS requests
Basically, any 500 Internal Server Error returned from the server would be considered by clients an unhandled condition / bug and potential security risk that should be reported and needs to be fixed.
