I agree with Rob, but I think what you are talking about is customized error pages. I use them at work especially for 128-bit encryption requirements.
The server has a default error page set somewhere, and to do this you'll need access to it. We set ours up so if the client has Javascript enabled, we do a redirect and pop a small window telling them they are being redirected and why. If Javascript is not enabled, they get a customized error page explaining the situation and gives them a link to the https equivalent of the page they requested, which is derived dynamically.
The key, though, is having access to your error pages.
HTH,
Jim Hawley