-----Original Message----- From: Jason Bainbridge > Hence I'm looking for a means of trapping that error for either a > re-direct, or to an error page. HTTP 1.1 seems not to class that as an > error, hence I'm looking for another way to access that 'bad' state. I don't think you can do anything about that, I don't think a request even hits the server for it, install ieHttpHeaders (google it) and monitor the request/response headers to see what is going on but I'm fairly sure you won't see anything hitting the server from that back button press.
Aaarggh! Thanks Jason, appreciated. Now I know I'm chasing shadows I'll address that differently. regards DaveP. -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]