Returning HTML with an error message works in response to an error for the main web page the browser is loading, but if a resource off of that page creates a problem, that doesn't work. For example, see the error below which was a twimg.com load from twitter.com. Not clear at this time how to handle this situation.
Thread-7:Perspectives.NotaryResponses: Checking time Wed May 11 03:43:53 2011
Thread-7:Perspectives.NotaryResponses: Not enough notaries to make quorum (2)
Thread-7:Perspectives.Policy: Quorum duration is 42683
Thread-7:Handler: Perspectives check failed: Policy check failed on 6c:4f:7a:12:47:29:15:a0:7d:fd:5e:1a:02:8d:e2:d9 for si1.twimg.com:443,2: Certificate not valid long enough (only 42683 seconds)
Thread-7:Handler: Deferring handling error connecting to server:
Policy check failed on 6c:4f:7a:12:47:29:15:a0:7d:fd:5e:1a:02:8d:e2:d9 for si1.twimg.com:443,2: Certificate not valid long enough (only 42683 seconds)
Thread-7:Handler: Responding to client.
Thread-7:Handler: Starting SSL with client...
Thread-7:Handler: SSL with client successful
Thread-7:Handler: Handling server error
Thread-7:Handler: Client request was: GET /a/1305134263/javascripts/api.bundle.js HTTP/1.1
Thread-7:Handler: Done.
Returning HTML with an error message works in response to an error for the main web page the browser is loading, but if a resource off of that page creates a problem, that doesn't work. For example, see the error below which was a twimg.com load from twitter.com. Not clear at this time how to handle this situation.