exception error raised in sslstart

[lnminente]

Very glad it helps on its first day!! It supports the idea of "Everyone can write filters and maintain them"

Just, i would like to remember here what Oddisey said, give a rating to the posts you liked

[z12]

I used to get the SSL error quite frequently.
I think I endup up using sidki's dll's, but still had problems.

Graycode Wrote:I was wondering if the SSL was being pipelined and if that might be causing Proxo / OpenSSL to get confused about the state of the connection's conversation.

Hmmm...That's an interesting thought.
I used to use pipelining with Firefox, but disabled it.
As you said, not all sites play well with it.

I also used to use some filters that modified the "Connection" header, which I have since disabled or removed.
Proxo is configured to use http/1.1, but I've unchecked the "Local Connections persist for" checkbox.
As a side note, I do remove the "Proxy-Connection" out header.
Off hand, I can't remember the last time I've seen that error message.

I didn't have an issue with the https login on the vodafone or play.com sites.
As I don't have an account at either site, I was unable to proceed any farther.

When I get some time, I might try re-enabling pipelining and see what happens.

z12

[whenever]

Just tried to to disable pipelining in opera by unchecking "Enable HTTP 1.1 for proxy" but that doesn't help to reduce the ssl error.

The v_097b Graycode posted can't be used with Proxomitron with below error. The other versions just gave more error than sidki's so I ended up sticking with sidki's.

[lnminente]

At the page's bottom of the German Proxomitron there is the 0.9.6m compatible with proxomitron...

[whenever]

Thanks lnminente! Just tried it but not better than sidki's.

[z12]

How about some links to sites which raise that error?

z12

[whenever]

(Dec. 04, 2008 02:12 AM)whenever Wrote:  So far I am filtering only one https site and the error happened occasionally. It usually happened after I have been using that site for a while. Some day it worked and some day the error rose up. Each time the error rose up, I have to restart Prox to be able to filter https again.

It's an invitation only forum but the invitation is currently closed.

Will some javascript activities cause the ssl error? I am using sidki's filter set and noticed that sometimes the ssl error rose up right after I clicked somewhere on the page, it's the time when the sidki's menu icon going to show up.

[z12]

whenever Wrote:So far I am filtering only one https site and the error happened occasionally. It usually happened after I have been using that site for a while. Some day it worked and some day the error rose up.

Being that the error is intermittent make it more difficult to pinpoint.

whenever Wrote:Will some javascript activities cause the ssl error? I am using sidki's filter set and noticed that sometimes the ssl error rose up right after I clicked somewhere on the page, it's the time when the sidki's menu icon going to show up.

I suppose it's possible that it could be menu related.
In sidki's config, it looks like a browser request is made to load menu data.
This occurs (more or less) on the first mouse click.

You might try clearing the log window before clicking on the page.
If you get an error, the log window might provide a clue.

z12

[whenever]

(Dec. 09, 2008 11:09 AM)z12 Wrote:  In sidki's config, it looks like a browser request is made to load menu data.

The request was then redirected to: http://local.ptron/sidki_h_2008-01-02/proxjs-x-menu.js.

(Dec. 09, 2008 11:09 AM)z12 Wrote:  You might try clearing the log window before clicking on the page.
If you get an error, the log window might provide a clue.

I just played for a long time by clearing the log window every time before I clicked on the page for the prox menu or clicked on a link, but there was nothing special in the log window when the ssl error raised up.

The errors raised up mostly when clicking on a link and seldom (none during this test) on the prox menu. I guess the prox menu might not be the cause, maybe it was because there was other ssl requests in the backgroud.

[z12]

I just installed the latest version of Opera.
They seemed to have resolved my major complaint, so I'm going to give it a try for awhile.
I didn't see an option to disable pipelining, but I'm not familiar with configuring it.

I did run across a site where Opera complained about the certificate, but didn't get an error.
So far, I've only come across a couple of secure sites with Opera.
If you find any other sites with the error, post a link.
I'll do the same.

z12

[lnminente]

People having problems with SSL try this filter. I don't filter SSL connections so i don't know if it helps

Code:

[HTTP headers]
In = FALSE
Out = TRUE
Key = "Connection: Don't keep alive {ln}081227 (out)"
Match = "Keep-Alive*"
Replace = "Close$LOG(w$DTM(c): Connection: Don't keep alive in \u)"

[whenever]

Just tried the above filter but it doesn't help to reduce the ssl error.

[lnminente]

Just trying, thanks Whenever

[whenever]

I am tired with the ssl error.

Does anybody know a proxy app that can do ssl decryption? Is it possible to chain it before Proxomitron for filtering the decrypted content? I remember sidki had said it was too late if the browser already saw the https and the browser would expect the content to be SSLed.

[Oddysey]

(Jan. 04, 2009 11:23 AM)whenever Wrote:  I am tired with the ssl error.

Does anybody know a proxy app that can do ssl decryption? Is it possible to chain it before Proxomitron for filtering the decrypted content?

There are quite a few of them, but how useful and/or stable they are, I couldn't tell you. I do see that the majority of them are for *nix-based machines, but Windows boxes do have some proggies that might do the job. (After all, that's why the library is available on nearly every platform/OS, it's meant to be used for developing just what you've been asking for.) Google shows me this:

http://www.google.com/search?hl=en&q=pro...%20windows

(Jan. 04, 2009 11:23 AM)whenever Wrote:  I remember sidki had said it was too late if the browser already saw the https and the browser would expect the content to be SSLed.

Not true. The browser will accept anything it can handle (natively or with a BHO), the reason being that the rendering engines are not tied to the request queue. Were it otherwise, then we'd never need to fiddle with MIME content filters and such.

HTH



Oddysey