Proxomitron Reborn

[amy]

(Apr. 26, 2019 02:47 AM)whenever Wrote:  - Make the config and lists to use utf-8 encoding

Is there a specific reason for this feature request? Currently, Proxomitron is "encoding-agnostic" --- or perhaps more precisely, "encoding-ignorant". It matches bytes with bytes. I have seen lots of other systems break when given unusual-yet-reasonable inputs because they weren't, and Proxomitron gets subjected to lots of such input, so I am in general against adding such a fragile layer of complexity.

(Apr. 26, 2019 02:47 AM)whenever Wrote:  - For now Proxomitron can match on bytes like [%E9][%AB][%98][%E7]. Please make it capable of replacing with bytes too. Maybe via a command like $HEX([%E9][%AB][%98][%E7]).

I believe if you write directly "éｫ˜ç" in the replacement dialog, you will get the behaviour you desire. Some more escapes would be nice, however, so this has been added to the list of feature requests.

(Apr. 26, 2019 02:47 AM)whenever Wrote:  - For the debug view, Proxomitron always return "Content-Type: text/html" while the server may return "Content-Type: text/html; charset=UTF-8". With the charset absent, the browser always takes the default value of ISO-8859-1, which will usually cause problems on non-western pages. The suggest is to let Proxomitron to return what the server returns on Content-Type header.

Added to feature request list.

(Apr. 30, 2019 09:16 AM)whenever Wrote:  If you have https filtering enabled, clicking Abort while Active connections is NOT 0 will make Proxomitron refuse accepting new connections.

Abortion is difficult. I haven't been able to reproduce(pun not intended) this, and I've been using https filtering for years, but I have a feeling I know what's causing it --- this is a design defect which has always been there in Scott's releases, that I haven't had the time to fix, because a full fix is not easy, but I've increased the priority of it now that you're seeing problems. (Technical details: Instead of closing all active connection socket handles, it just keeps track of the minimum and maximum socket handles, and closes them all by looping through them sequentially. It's a quick-and-dirty way to add this function, but may end up closing some other unrelated handles too. I was actually a bit shocked when I first discovered this.)

(Apr. 30, 2019 09:16 AM)whenever Wrote:  While the Aborting is finished, the log window shows below message. Seems to be a ports binding issue.

Code:

Listening on port 8443
Listening on port 8080

The problem doesn't appear to happen if you have https filtering disabled (Untick Use SSLeay/OpenSSL in HTTP tab of the settings).

That is the normal message and has nothing to do with the defect mentioned above. Using OpenSSL filtering may change the memory allocation and general environment enough to make it appear.

(Apr. 30, 2019 09:16 AM)whenever Wrote:  1. The debug view shows incoming headers now. What about showing outgoing headers (with any header filters applied) too?

Added to feature request list.

(Apr. 30, 2019 09:16 AM)whenever Wrote:  2. Improve the proxy testing function.
...
The suggest is to make the destination a user configurable external URL.

Added to feature request list.

(Apr. 30, 2019 09:16 AM)whenever Wrote:  3. Port Proxomitron to Linux world so that we can run it on our routers. A command line only version is enough.

That's not a feature request, that's more like a "new version" request! Not to say I won't do it, however, because one of other items already on the list is "Android support". That won't be any time soon, as you may expect...