There were 5 different errors I got during that time, here are the last 3 i recorded >
~
~
For a website when it is database driven - it pulls the stored data, saves the new data constantly depending on the request from the users.
When it comes to pulling data and when it's too many data to pull (say entire table for merit history) sometimes it cross the default time defined by the database server. The user ends up seeing error then.
When too many users (client side) are interacting with the database (server side) at the same time then because of the bandwidth limitation and/or possible other factors, a database server can refuse request. The user will end up seeing error.
Anyway I guess the below references will give you a decent idea.
503
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may wish
to simply refuse the connection.
504Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may wish
to simply refuse the connection.
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
Note: Note to implementors: some deployed proxies are known to
return 400 or 500 when DNS lookups time out.
Note: Note to implementors: some deployed proxies are known to
return 400 or 500 when DNS lookups time out.
It just made me think how beautiful the forum will be if there is a badge underneath the username.
