Opened 6 years ago

Closed 4 years ago

#11826 closed enhancement (wontfix)

Distinguish between permanent and temporary Onionoo errors

Reported by: karsten Owned by: isis
Priority: Medium Milestone:
Component: Metrics/Globe Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Copied from #8667, also applies to Globe:

As of now, Onionoo has a "maintenance mode" that I'm planning to use very rarely. But sometimes it's necessary to shut down Onionoo to support new features or fix bugs. During this time, Onionoo responds to all requests with a 503 Service Unavailable status code. Atlas should respect this code and display a different warning than:

"Backend error! The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted it may mean that there is an issue with your browser/add-ons. Please report which browser/addons/etc. you're using to the bug tracker."

How about this warning?

"Backend temporarily unavailable! The backend server is temporarily unavailable. If this issue persists for more than a few hours, please report it using the <a href="">bug tracker</a>."

On a related note, should Atlas also distinguish between 400 Bad Request and 500 Internal Server Error (or 4xx and 5xx codes) by telling the user that the issue can more likely be found in the front-end or back-end? That would make for slightly better bug reports, I guess. now lists HTTP response codes and suggests actions. Pasting here for simplicity:

Response codes: Clients should handle response codes by distinguishing between client and server errors, and if there's a problem, informing their users about the kind of problem. The following response codes are used:

  • 200 OK: The request was processed successfully.
  • 304 Not Modified: Server data has not changed since the "If-Modified-Since" header included in the request.
  • 400 Bad Request: The request could not be processed either because the requested resource could not be found or because of bad syntax. This is most likely a client problem.
  • 500 Internal Server Error: There is an unspecific problem with the server which the service operator may not yet be aware of. Please check if there's already a bug report for this problem, and if not, file one.
  • 503 Service Unavailable: The server is temporarily down for maintenance, or there is a temporary problem with the server that the service operator is already aware of. Only file a bug report if this problem persists.

Child Tickets

Change History (3)

comment:1 Changed 5 years ago by isis

Owner: changed from rndm to isis
Status: newassigned

Changing Globe tickets to be owned by isis.

comment:2 Changed 5 years ago by isis

Status: assignednew

comment:3 Changed 4 years ago by karsten

Resolution: wontfix
Severity: Normal
Status: newclosed

We're shutting down Globe, and we still have #8667 for the same issue in Atlas. Closing as won't fix.

Note: See TracTickets for help on using tickets.