exception error raised in sslstart

[sidki3003]

(Jan. 07, 2009 11:31 AM)ProxRocks Wrote:  

(Jan. 07, 2009 03:57 AM)Oddysey Wrote:  Given the above, Proxo can indeed be said to be accessing, and filtering on, another port besides 80/443. A bit strange that Scott never mentioned this...

to clarify, Proxo does perform DNS Port 53 lookups, however, that does NOT mean that Proxo can FILTER DNS Port 53 lookups...

It seems we have a misunderstanding regarding local and remote ports here.

http://www.geocities.com/sidki3003/prox/...tc/FAQ.txt :

Quote:Q3: What local ports are involved in the request/response chain?

A3: Prox listens locally on port 8080 (by default), the browser sends its
request from a low range random port to 8080, Prox opens a low range
random port and sends the request to the outside world (usually remote
port 80), the reply from the outside world is addressed to this same port,
Prox sends the reply from port 8080 to the local port that the browser
previously opened.

IOW:
Proxomitron listens on one single local port for incoming (by default local) user-agent HTTP(S) requests, filters their headers, then forwards them.

It doesn't matter at all, to which remote port the forwarded request is going. However, usually it's port 80. Sometimes 443, sometimes 8080, sometimes a random port.