Sidki, Grypen

[Siamesecat]

Oddysey,
You are correct! It was the cookie content filter that was opening the log window. I had it writing to the log window, but it never used to open it by itself. I removed the logging part from the code, and it no longer opens the window.
Any suggestions for fixing the HTTPS filtering problems?

[Oddysey]

'cat;

Sorry I wasn't more quick to respond, I don't visit so often since I was castigated last year for my views. But I'm still glad to help, whenever and wherever I can.

I reviewed your question, it appears that your system is having an issue with decrypting secure pages, yes? And you attribute that to "old" files..... Before I go any further, keep in mind that I am not a professional, so I can only speak from personal experience. But I have to say that I haven't upgraded from the two modified files found in the usual locations around the web, dated 9/26/2006. I don't think I'm having any issues, but it could be that I visit encrypted sites only occasionally, and not very many of them at that.

Can you give us an example site/page? If your problems arise on pages that contain privacy info, then perhaps you might want to set up a temporary "fake" account, just for testing purposes.



Oddysey

[Siamesecat]

I presumed the problem was caused by older ssleay32.dll and libeay32.dll files acting on current pages because I only began having it fairly recently. Prox will not work with versions newer than 2006. I would get error message boxes popping up instead of going to the next page I selected.
What does "Exception [C0000005] raised in SSLStart" mean? That is the message I get.

An example is the Mozilla addons page:
https://addons.mozilla.org/en-US/firefox/
The first page would work fine with Firefox, but trying more pages would only cause the error message boxes. It might not be the encryption algorithm that is the problem. I really have no idea.
I just tried it with Opera (just installed yesterday), and a few pages actually worked, but now am getting only the error messages.