ProxHTTPSProxy, a Proxomitron SSL Helper Program

[JJoe]

(May. 29, 2010 03:45 PM)whenever Wrote:  JJoe, could you please see if the 0.2c works on your system?

I believe it does.

(May. 29, 2010 03:45 PM)whenever Wrote:  

(May. 28, 2010 06:04 PM)Graycode Wrote:  You've already encountered Polipo refusing non-SSL through that port,

Polipo is not refusing non-SSL through port 443. What JJoe met is a bug of the 307 redirecting which has been addressed since version 0.2b (I hope so).

I think my Polipo is simply refusing non-SSL through 443.
In the log that follows, Proxo was set to use Polipo on port 8123

Quote:+++GET 1752+++
Using Proxy - 127.0.0.1:8123
GET http://ssl.scroogle.org:443/ HTTP/1.1
Host: ssl.scroogle.org:443
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Cache-Control: max-age=0
Connection: keep-alive
Browser reload detected...

+++RESP 1752+++
HTTP/1.1 403 Forbidden port
Connection: keep-alive
Date: Sat, 29 May 2010 19:00:57 GMT
Content-Type: text/html
Content-Length: 468
Pragma: no-cache

Quote:403 Forbidden port

The following error occurred while trying to access http://ssl.scroogle.org:443/:

403 Forbidden port
Generated Sat, 29 May 2010 14:00:57 Central Daylight Time by Polipo on E3-PC:8123.

EDIT:
I should add that at the moment this does not matter. ProxHTTPSProxy is 'correcting' the address before Polipo sees it. Which is probably what whenever meant to say.