Changes between Initial Version and Version 1 of Ticket #2452


Ignore:
Timestamp:
May 14, 2021, 7:00:27 AM (3 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2452 – Description

    initial v1  
    11**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)
    22
    3 ----> This should be used when there are no rasservers to process request.
     3-> This should be used when there are no rasservers to process request.
    44
    55The 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.
    … …  
    77if 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).
    88
    9 ----> Syntax errors in WCPS requests
     9-> Syntax errors in WCPS requests
    1010
    1111Basically, 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.