On Thu, 3 Nov 2005, slu wrote:
alan wrote:
I haven't yet seen a way to intercept the 400 Bad Request type errors.
Can someone point me to where in could find info on all the errors that may
come up using the gecko engine & how to intercept them if possible?
400 Bad Request is not a Gecko error but the HTTP response code.
You can use nsIWebProgressListener to grab the response header
and parse for the code yourself.
Do you know where there's an example of this?
I've had the same question.
The header for nsIWebProgressListener isn't clear
to me at all.
_______________________________________________
mozilla-embedding mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-embedding
