More versatility with user suspension pages
At present, suspension requests are sent through a CGI script (/cgi-sys/suspendedpage.cgi) which renders the HTML page displayed to the end user. The issue with this is that high-traffic sites can continue to use excessive resources due to the behavior of this process, and it offers little control for the administrator.
So as a system administrator, I would like the ability to choose the behavior of suspended websites. This would ideally be selectable from the following options:
a) Render the template (existing behavior)
b) Redirect to a URL
c) Pipe the request to a script
d) Respond with a code (401, 403, 404, etc)