Ben Thorner 39e03cee50 Remove redundant 413 error page ...

This was used when there was an Nginx instance sitting in front of
Admin [1], but nowadays traffic goes through CloudFront, where we
decided not to implement the same protection:

- The likelihood of large requests being a security threat is small
because it's a difficult attack vector.

- We have put in place specific limits on routes where we the size
of the request is actually important [2].

Note that the other error pages can all still be used based on the
response code we get from API requests [3]. Also worth noting we've
had 0 413 response codes for Admin in the last month.

[1]: https://github.com/alphagov/notifications-aws/blob/master/ansible/roles/nginx/templates/nginx.conf.j2#L29-L30
[2]: https://github.com/alphagov/notifications-admin/pull/4090
[3]: https://github.com/alphagov/notifications-admin/blob/b3c0abc4966c847b9a4ccc33a1cf1a148620261e/app/__init__.py#L407-L416

2021-12-09 14:48:34 +00:00

..

401.html

Fix sign in link on 401 page

2021-04-08 08:42:02 +01:00

403.html

Don’t allow paragraphs without class attribute

2020-05-29 17:11:01 +01:00

404.html

Don’t allow paragraphs without class attribute

2020-05-29 17:11:01 +01:00

410.html

Don’t allow paragraphs without class attribute

2020-05-29 17:11:01 +01:00

500.html

Don’t allow paragraphs without class attribute

2020-05-29 17:11:01 +01:00