Posted by
April, 13, 2003
The following has been announced by the author of the Proxomtiron. As he has already noted within the readme.txt as well as the changlog.txt files this beta has many new functions including the ad of a a new Dom filter.
Quote by Scott R. Lemmon - Proxomition's Author
I'm releasing a kind of "limited" beta test for the next version of Proxomitron (no fanfare yet - I just plan to mention it on the forums and list). Quite a lot has changed under the hood and I want to do kind of a test run to shake out any new bugs. Still, anyone who's interested in checking it out can grab it from here..."
New Stuff in Naoko 4.5 (beta)
* Try http://local.ptron/.pinfo/ - lots of stuff there ^_^ (views can be customized via the Info.css in the html folder)
* Added ability to import/export filter to and from the windows clipboard. Right-click over either the web or header filter lists - the import/export options are available in the context menu.
Export will write any selected filters to the clipboard while import will insert filters from the clipboard's text. The format is the same as is used in Proxomitron's config files.
There's also an option in the merge dialog to accept input from the clipboard rather than a file. It can be used to import any config file settings - just be sure to include the filter section headers with the text.
* Log window clipboard should be better behaved under NT/W2k/XP
* Proxomitron now has support for pre-request variables. These can be set anywhere (even in the headers) and checked later (say in the actual HTML). Each request has it's own set, and is isolated from all other pages.
- To set a variable use... $SET(variable=something) - To clear a variable use... $SET(variable=) - To get a variable's value use... $GET(variable) - To test a variable's value use... $TST(variable=match expression) or also just... $TST(variable) can be used in a match to see if the variable's contents match the current text. For example.. src="http://$TST(myhost)/" note that this must be a literal match (except for case) - the variable's value isn't treated as a matching expression with wildcards and such.
Unlike positional "1 2 # ..." style variables, $SET expands a named variable's value as soon as it's called (positional are expanded in the replace). That means named variables can be set to themselves and expanded - for instance...
$SET(foo=$GET(foo) more stuff) - adds to the end of "foo" $SET(foo=more stuff $GET(foo)) - adds to the start of "foo" $SET(foo=$GET(foo) 1) - adds value of "1" to the end of "foo" $SET(foo=$GET(foo)$GET(bar)) - adds value of "bar" to the end of "foo"
$TST can also be used on good-old positional type variables ... 9 which allows you to do neat things like...
<1s * </$TST(1)>
which matches...
stuff
but not...
stuff
Note that to get this to work I had to make some big changes to the way Proxomitron normally sets these variables. In this beta please watch out for unexpected side-effects. Especially in cases where you use the same variable more than once in a match. Proxomitron used to wait till the very end to set variables which guaranteed that once matched it wouldn't change till matched again. Now it may be possible for some failed match later on to erase the previous value of a variable. Still I can't really find many cases where this would actually be a problem and the trade off is probably worth it.
Speed notes:
Like calling a list, testing a variable is a bit costly It involves a lookup of it's name each time it's called so it's better to not have it as the very first thing in a match..
Source from Scott R. Lemmom: Proxomitron 4.5 beta !!
Any comments , bug reports and/or questions can be added to the above thread.
You can syndicate our news using the file RSS 0.91, ultramode.txt, or RSS 1.0.
