Opened 3 years ago

Last modified 2 years ago

#65 new defect

Custom 502 and 503 pages for crin.org

Reported by: chris Owned by: chris
Priority: major Milestone: Maintenance
Component: crin1 Version:
Keywords: Cc: peter
Estimated Number of Hours: 0 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0.6

Description

It would be more informative if there were custom 502 and 503 error pages for https://www.crin.org/ rather than the default Nginx ones.

I will write up some details below on the 502 and 503's we seeing getting, see also ticket:54.

I'm happy to create a static 502 and static 503 error page and will look at adding it to the git repo.

Change History (2)

comment:1 Changed 3 years ago by chris

  • Add Hours to Ticket changed from 0 to 0.1
  • Total Hours set to 0.1

comment:2 Changed 2 years ago by chris

  • Add Hours to Ticket changed from 0 to 0.5
  • Total Hours changed from 0.1 to 0.6

Peter, we could do with a custom 503 (and 502) error page for https://www.crin.org/ -- if a client requests more than 6 .php pages in one second they are served the default Nginx 503 error document and this doesn't explain what happened, if we had a custom page which had something like the following text on it:

Sorry you are requesting pages too quickly from this server, you need to request less than 6 a second if you want to be served the page you want.

Then it might encourage clients reduce their request rates?

Yesterday for example, one hundred and forty seven 503 errors were served to "Mozilla/5.0 (compatible; SemrushBot/1.1~bl; +http://www.semrush.com/bot.html)" between 05/May/2016:21:40:33 and 05/May/2016:21:46:09 (in this case I'm not so worried -- see the comments on projecthoneypot.org, but on other days it does look as if some legitimate clients run into this issue).

Can you, or should I, add a static .html page to the git docroot?

The Nginx config needed is quite simple, for example:

error_page 503 /503.html;
Note: See TracTickets for help on using tickets.