Proxomitron Update?

  • Thread starter Thread starter nocando
  • Start date Start date
N

nocando

I've noticed a few sites carrying what they refer to as an update to
Proxomitron. NoNags has had it for a few days. Lonnie's WebBlog Newsletter
covered it today.
It's still reads as version 4.5 which was available last year. Anyone d/l
it and use it yet and is there anything different in it?

nocando
 
nocando said:
I've noticed a few sites carrying what they refer to as an update to
Proxomitron. NoNags has had it for a few days. Lonnie's WebBlog Newsletter
covered it today.
It's still reads as version 4.5 which was available last year. Anyone d/l
it and use it yet and is there anything different in it?

nocando

Without any URLS to check out for you, I would guess that the updates it
refers to are changes to the filters it uses. Proxomitron is a program
that doesnt need updates per se, but can be altered by changing the
filters it uses.
For example:
If you are using a filter for google that filters out the ads...and
google updates their site, then proxomitron will no longer 'work'.
The updates that I have seen for it simply adjusts what it "looks for"
on popular sites.
 
nocando said:
I've noticed a few sites carrying what they refer to as an update to
Proxomitron. NoNags has had it for a few days. Lonnie's WebBlog Newsletter
covered it today.
It's still reads as version 4.5 which was available last year. Anyone d/l
it and use it yet and is there anything different in it?

I saw this at the Nonags site. However, they didn't have a section it
was listed under and no more information than that. I Google it, but
couldn't find out anything more.
 
I've noticed a few sites carrying what they refer to as an update to
Proxomitron. NoNags has had it for a few days. Lonnie's WebBlog Newsletter
covered it today.
It's still reads as version 4.5 which was available last year. Anyone d/l
it and use it yet and is there anything different in it?

nocando

Hi, here is the overview of the differences taken directly from

http://www.proxomitron.info/files/may-vs-june.shtml
==========================================================

PROXOMITRON 4.5 -- May vs. June
Operational differences between the two Naoko 4.5 releases

The Remote Proxy "Direct Connection Fail-Back" Feature
The May version contains an undocumented new feature related to remote
proxy connections: In the event of a connection failure with a remote
proxy, Proxomitron will "fail back" to a direct connection with the
requested URL. (A warning is initiated when the connection to the
remote proxy has failed, but there is no warning that Proxomitron is
about to establish a direct connection with the site.) Due to a bug,
however, this behavior is not exhibited if Proxomitron is set to
rotate through multiple proxies: Should connection failure occur with
one of the proxies during rotation, Proxomitron will then attempt
connection with the next proxy in the list. In the event that all
listed proxies suffer connection failure, Proxomitron will become
caught in an "infinite loop" as it continues to attempt connection
with each proxy in rotation, instead of failing back to a direct
connection.

The June version of 4.5 does not contain the feature to "fail back" to
a direct connection, nor does it contain the "infinite loop"
proxy-rotation bug.


The Merge Bug
The May release also contains a notable Merge bug: After merging an
input file, the current config name displayed by Proxomitron in its
title bar is changed to the name of the input file -- afterwards, when
the user saves their config using the "blue disk" icon, the input file
is overwritten instead of the user's config file. When Proxomitron is
restarted, naturally the user is perplexed to find that merged filters
and subsequent edits were apparently not saved. The user can correct
the problem during the bug-occurring session by using the File
dropdown menu's "Save Config File" and resaving to their current
config's filename (which will also restore the display of the config's
filename in the program's title bar) -- or, if Proxomitron was already
closed and restarted, the user can Load (not Merge!) the overwritten
input file and then use the File dropdown menu to save it to their
usual config's filename. To avoid problems with the Merge bug, the
user should just use the dropdown menu to save the config after each
Merge, not the blue disk icon.

The June version of 4.5 does not contain the Merge bug.


In Summary...
The May version's feature to "fail back" to a direct connection should
provide the user of a remote proxy (such as a caching proxy) with a
direct-accessing connection in the event of proxy failure; however,
this feature is impractical for use with a remote "anonymizing" proxy
since the main purpose for using one is to avoid revealing the user's
true IP. The June version was primarily released to resolve this
issue with anonymizing proxies, which is why the fail-back feature is
removed from it -- but it has also been corrected for bugs found in
the May version. The June version is therefore the "final" 4.5
release, while the May version remains available for those who
specifically need the fail-back behavior when using a single remote
proxy. The May release of Naoko 4.5 is the only version of
Proxomitron having this "direct connection fail-back" feature.
 
nocando said:
I've noticed a few sites carrying what they refer to as an update to
Proxomitron. NoNags has had it for a few days. Lonnie's WebBlog Newsletter
covered it today.
It's still reads as version 4.5 which was available last year. Anyone d/l
it and use it yet and is there anything different in it?

nocando

It's still available here, on the 'files' page.
http://www.proxomitron.info/

FredD
 
Night2000 said:
Hi, here is the overview of the differences taken directly from

http://www.proxomitron.info/files/may-vs-june.shtml
==========================================================

PROXOMITRON 4.5 -- May vs. June
Operational differences between the two Naoko 4.5 releases

The Remote Proxy "Direct Connection Fail-Back" Feature
The May version contains an undocumented new feature related to remote
proxy connections: In the event of a connection failure with a remote
proxy, Proxomitron will "fail back" to a direct connection with the
requested URL. (A warning is initiated when the connection to the
remote proxy has failed, but there is no warning that Proxomitron is
about to establish a direct connection with the site.) Due to a bug,
however, this behavior is not exhibited if Proxomitron is set to
rotate through multiple proxies: Should connection failure occur with
one of the proxies during rotation, Proxomitron will then attempt
connection with the next proxy in the list. In the event that all
listed proxies suffer connection failure, Proxomitron will become
caught in an "infinite loop" as it continues to attempt connection
with each proxy in rotation, instead of failing back to a direct
connection.

The June version of 4.5 does not contain the feature to "fail back" to
a direct connection, nor does it contain the "infinite loop"
proxy-rotation bug.


The Merge Bug
The May release also contains a notable Merge bug: After merging an
input file, the current config name displayed by Proxomitron in its
title bar is changed to the name of the input file -- afterwards, when
the user saves their config using the "blue disk" icon, the input file
is overwritten instead of the user's config file. When Proxomitron is
restarted, naturally the user is perplexed to find that merged filters
and subsequent edits were apparently not saved. The user can correct
the problem during the bug-occurring session by using the File
dropdown menu's "Save Config File" and resaving to their current
config's filename (which will also restore the display of the config's
filename in the program's title bar) -- or, if Proxomitron was already
closed and restarted, the user can Load (not Merge!) the overwritten
input file and then use the File dropdown menu to save it to their
usual config's filename. To avoid problems with the Merge bug, the
user should just use the dropdown menu to save the config after each
Merge, not the blue disk icon.

The June version of 4.5 does not contain the Merge bug.


In Summary...
The May version's feature to "fail back" to a direct connection should
provide the user of a remote proxy (such as a caching proxy) with a
direct-accessing connection in the event of proxy failure; however,
this feature is impractical for use with a remote "anonymizing" proxy
since the main purpose for using one is to avoid revealing the user's
true IP. The June version was primarily released to resolve this
issue with anonymizing proxies, which is why the fail-back feature is
removed from it -- but it has also been corrected for bugs found in
the May version. The June version is therefore the "final" 4.5
release, while the May version remains available for those who
specifically need the fail-back behavior when using a single remote
proxy. The May release of Naoko 4.5 is the only version of
Proxomitron having this "direct connection fail-back" feature.

I think they're talking about 2003:

"There were two separate releases of Proxomitron 4.5, one in May of
2003 and one in June."

This "update" to Proxomitron is most likely a hoax or a mistake.

Nonags:

http://www.nonags.com/nonags/wwn.html

doesn't have a link or even a description for the "update".
 
Night2000 wrote:
I think they're talking about 2003:

"There were two separate releases of Proxomitron 4.5, one in May of
2003 and one in June."

This "update" to Proxomitron is most likely a hoax or a mistake.

Nonags:

http://www.nonags.com/nonags/wwn.html

doesn't have a link or even a description for the "update".

You may be right, I checked out the link at NoNags, and couldn't find
a description of the update either. Actually I went to a few top
places. SnapFiles, Softpile, and MajorGeeks. None of them even have
Proxomitron listed.

Night2000
 
Back
Top