ProxHTTPSProxy, a Proxomitron SSL Helper Program

[whenever]

(May. 20, 2010 06:01 AM)JJoe Wrote:  

Code:

+++SSL:RESP 1666+++
SSL cipher TLSv1 AES256-SHA (256 bits)
HTTP/1.1 307 Moved Temporarily
Location: http://ssl.scroogle.org:443/
+++CLOSE 1666+++

So, 307 response was successfully issued.

(May. 20, 2010 06:01 AM)JJoe Wrote:  http://local.ptron/.pinfo/urls/ shows

Code:

Closed    1673    000        0    http://ssl.scroogle.org:443/
Closed    1672    307        0    https://ssl.scroogle.org:443/

http request follows https request, that's what we expect.

(May. 20, 2010 06:01 AM)JJoe Wrote:  ProxHTTPSProxy's log window shows

Code:

ProxHTTPSProxy/0.1 serving on localhost:8081, <Ctrl-C> to stop ...
E3-PC - - [19/May/2010 23:06:41] "CONNECT ssl.scroogle.org:443 HTTP/1.1" 200 -
E3-PC - - [19/May/2010 23:06:47] "CONNECT ssl.scroogle.org:443 HTTP/1.1" 200 -

Only https requests here. Where are the http requests? Are you sure you have made Proxo to forward http requests to ProxHTTPSProxy too?

Let's bypass Proxo totally. Could you please test with the browser's http and https proxies both set to ProxHTTPSProxy?

(May. 20, 2010 06:01 AM)JJoe Wrote:  Probably too late for me to think straight but wouldn't the user be expected to maintain a list?

Yes, but it is Proxo that maintains the list while not ProxHTTPSProxy.

(May. 20, 2010 06:01 AM)JJoe Wrote:  Proxo could build a list for you, I think. Some sort of tag might remove the need.

What happens when https and http share an address or part of one?

That's what we have to think about later. After all it is just ver 0.1 now. The first thing is to get it running on your machine so you can take a hand in