ProxHTTPSProxyMII: Development

[whenever]

(Jul. 01, 2014 11:28 PM)JJoe Wrote:  Which file are you using?

I am using Win32OpenSSL_Light-1_0_1h.

I am not sure if a reboot after you update OpenSSL or pyopenssl would help, but I would try.

(Jul. 01, 2014 11:28 PM)JJoe Wrote:  After updating OpenSSL, I was seeing two consistent errors while using the exe:

I saw those too. The browser gave below information if you visit those urls directly.

Quote:Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.

This will be fixed in the next version.

(Jul. 01, 2014 11:28 PM)JJoe Wrote:  I am seeing a few Connection timed out

Timed out is normal in the network world, especially in GFWed China.

(Jul. 01, 2014 11:28 PM)JJoe Wrote:  Have seen a few [SSL: BAD_WRITE_RETRY] but these are requested again.

I haven't seen this ever, but let the browser do its job.

So for now the https://www.dsply.com/index.php?pid=GqeC...ller=37014 problem remains? I will look into it when I get time. I suppose it is urllib3 and Proxomitron related, because:

• The rear proxy doesn't complain, and the front proxy complain when Proxomitron in the chain.
• The older version that doesn't use urllib3 works.