manugarg / pactester

Automatically exported from code.google.com/p/pactester

Hello 👋, I am a software engineer, particularly interested in systems and reliability. My linkedIn profile has work related info, so won't repeat that here.

• My current blog (previous blog - last updated 2010).
• 🔭 I currently maintain the following projects outside of work:
  • Cloudprober - an active probing software used by a bunch of large organizations
  • Pacparser - C and python library to add PAC file parsing capability
  • Page Notes - a productivity chrome extension, not open-source
• My first big contribution to open-source was finding (and fixing, but finding was the hard part) a nasty bug in the squid web-proxy.
• In my previous life, as part of my system internals exploration, I wrote a bunch of articles. Following two articles are still referenced quite a lot, including in some university courses:
  • Sysenter Based System Call Mechanism in Linux 2.6
  • About ELF Auxiliary Vectors

pactester's Issues

Path matching

This is not really a bug but more of a FAQ about pac-files.

How can I include an optional slash (/) in a shExpMatch call?

That is, I want the browser to connect directly for both

http://host.local and
http://host.local/index.html

but

if (shExpMatch(url, "http://*.local/*")) { return proxy_no; }

does not match the first example since it requires a slash. However, I want
that slash there because local is frequent enough in the path or domain
name in other URLs, hence I want to distinguish between local as "TLD" and
local as part of the path or domain (this also applies to "lan" as "TLD").
Is that possible or do I need two expressions:

if (shExpMatch(url, "http://*.local")) { return proxy_no; }
if (shExpMatch(url, "http://*.local/*")) { return proxy_no; }

to achieve this?

Original issue reported on code.google.com by [email protected] on 21 Apr 2010 at 3:19

Install.sh doesn't work if path to installer has spaces

What steps will reproduce the problem?
1. Place the installer in a dir such that the path has spaces e.g. ~/my
stuff/pactester-vx
2. cd to build dir and run install.sh ~/tools or whatever

What is the expected output? What do you see instead?
A functional pactester - but get an empty file called pactester.


What version of the product are you using? On what operating system?
1.0.6 on OSX 10.4

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 21 Jun 2007 at 9:25

wrong netmask counting

MY WPAD.DAT FILE:
------------------------------------------------------
function FindProxyForURL(url, host)

{

    if (isInNet(myIpAddress(), "10.80.0.0", "255.240.0.0") &&

        (shExpMatch(url, "*mozilla.org/*")||
           shExpMatch(url, "*gazeta.pl/*")||

           shExpMatch(url, "*onet.pl/*")
        )

       )

       return "PROXY proxy.xxxx.pl:8080";

    return "DIRECT";

}
------------------------------------------------------
FOR MY QUERY:
./pactester -p wpad.dat -u http://www.onet.pl -c 10.90.100.41

I RECEIVE ANSWER:
DIRECT
------------------------------------------------------

i thing it should be PROXY,
because IP is in that network and URL is ok too.

Original issue reported on code.google.com by [email protected] on 4 Sep 2008 at 1:00

Incosistent results when using IP regex evaluation

Firstly, great thanks for a truly great tool!

I am using this tool to evaluate pac files on a regular basis and during 
an attempt to optimise pac files I think I stumbled on a bug...

I am using XP SP2 & the binaries 
from "http://pactester.googlecode.com/files/pactester-pacparser-1.0.8-
1.0.4-win32.zip" which I think are the latest & greatest.

I have attached 4 files, two pac files and two URL lists (urlslist) for 
evaluation.

URL lists; direct-urls.txt & internet-urls.txt
Pac files ; regex.pac & noregex.pac

If I use the regex pac file every second IP-notated entry fails. The pac 
file without regex contains the same config (bar the regex) and that works.

repeat this issue by testing;

.\pactester.exe -f .\internet-urls.txt -p .\regex.pac (works)
.\pactester.exe -f .\direct-urls.txt -p .\regex.pac (fails)
.\pactester.exe -f .\internet-urls.txt -p .\noregex.pac (works)
.\pactester.exe -f .\direct-urls.txt -p .\noregex.pac (works)

The reason I report this is because of the inconsistent failure (every 
second entry). That can be nasty...

Could I also suggest two small improvements to an otherwise perfect 
product?
1. Add version info ( -v or something) as an argument
2. Add the possibility of writing comments in the "urlslist" files 
"// comment goes in here" ?

Regards,

John

Original issue reported on code.google.com by [email protected] on 20 Oct 2009 at 1:45

Attachments:

• direct-urls.txt
• internet-urls.txt
• noregex.pac
• regex.pac

pactester doesn't handle URLs with port number well

If you don't specify host as a command line option and URL contains port
number then pactester considers port number to be part of hostname. For
further details see: 

http://groups.google.com/group/pactester/browse_thread/thread/e9be4cb951e7905

Original issue reported on code.google.com by manugarg on 1 May 2008 at 11:53

alert from PAC files

The current pactester doest implement alert() which most browsers allows. I
have a patch for it.

117 $js_context->function_set("myIpAddress", sub {my_ip});
118 $js_context->function_set("alert", sub { print "\n--------- ALERT
---------\n@_\n-------------------------\n"; });
119
120 # Evaluate pac_utils.js and PAC file
121 my $rc = $js_context->eval($nspac);

Please let me know.

Cheers

Original issue reported on code.google.com by [email protected] on 13 Dec 2007 at 4:19

Does not install on OS X Snow Leopard

What version of the product are you using? On what operating system?

1.0.8 on OS X Snow Leopard 10.6.1

Please provide any additional information below.

In the log:

---8< cut here >8---

cc -o Darwin_DBG.OBJ/jsprf.o -c -Wall -Wno-format -g -DXP_UNIX -DSVR4 -DSYSV -
D_BSD_SOURCE -DPOSIX_SOURCE -DDARWIN -DX86_LINUX  -DDEBUG -DDEBUG_root -
DEDITLINE -IDarwin_DBG.OBJ  jsprf.c
jsprf.c: In function 'BuildArgArray':
jsprf.c:620: error: incompatible types in assignment
make[1]: *** [Darwin_DBG.OBJ/jsprf.o] Error 1
make: *** [all] Error 2
install: illegal option -- D
usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
               [-o owner] file1 file2
       install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
               [-o owner] file1 ... fileN directory
       install -d [-v] [-g group] [-m mode] [-o owner] directory ...
x JavaScript-SpiderMonkey-0.17/
x JavaScript-SpiderMonkey-0.17/README

---8< cut here >8---

and

---8< cut here >8---
x JavaScript-SpiderMonkey-0.17/Changes

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This module requires the SpiderMonkey C library -- please read the
README file on how to download, compile and link it.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

sed: 1: "Makefile": invalid command code M
sed: 1: "Makefile": invalid command code M
sed: 1: "Makefile": invalid command code M
make: *** No targets specified and no makefile found.  Stop.
make: Nothing to be done for `install'.
strangelove:build eelco$ pactester
-bash: pactester: command not found
strangelove:build eelco$ cd ..
strangelove:pactester-1.0.8 eelco$ ./pactester 
Can't locate JavaScript/SpiderMonkey.pm in @INC (@INC contains: 
/Library/Perl/Updates/5.10.0 
/System/Library/Perl/5.10.0/darwin-thread-multi-2level 
/System/Library/Perl/5.10.0 
/Library/Perl/5.10.0/darwin-thread-multi-2level /Library/Perl/5.10.0 
/Network/Library/Perl/5.10.0/darwin-thread-multi-2level 
/Network/Library/Perl/5.10.0 
/Network/Library/Perl 
/System/Library/Perl/Extras/5.10.0/darwin-thread-multi-2level 
/System/Library/Perl/Extras/5.10.0 .) at ./pactester line 31.
BEGIN failed--compilation aborted at ./pactester line 31.
---8< cut here >8---

br,
Eelco

Original issue reported on code.google.com by [email protected] on 22 Sep 2009 at 8:01

Patch for Issue#2 /trunk/pactester

Please see http://code.google.com/p/pactester/issues/detail?id=2 for details

Original issue reported on code.google.com by [email protected] on 13 Oct 2012 at 1:18

Attachments:

• pactester.patch

Add support for Microsoft PAC extensions for IPv6.

These extensions are used by Google Chrome as well. These extensions include - 
dnsResolveEx, myIpAddressEx and isResolvableEx. 

(There are a few more defined by Microsoft, but not implemented by Google 
Chrome. For detailed list look here - 
http://blogs.msdn.com/b/wndp/archive/2006/07/18/ipv6-wpad-for-winhttp-and-winine
t.aspx)

pacparser and pactester should support these new extension - at least the ones 
supported by Google Chrome. 

Original issue reported on code.google.com by manugarg on 29 Jun 2010 at 7:27

Weekday range does not work well

What version of the product are you using? On what operating system?
I am using pactester-pacparser-1.0.4-1-win32 on Windows XP OS

Please provide any additional information below

To me it seems the weekday range is not working accordingly. When I
specified weeks day range as 
if(weekdayRange("MON", "SAT"))
   {

     return "PROXY 134.244.163.209:8080";

   }
   else
   { 
     return "PROXY 134.244.163.211:3128";
   }


on Friday at local times 18:50:30 and 22:30:56 ,

I get "PROXY 134.244.163.211:3128" as return ,which
is incorrect. Please look into this

thanks
Karandeep Malik

Original issue reported on code.google.com by [email protected] on 31 Jul 2009 at 5:11

isInNetEx not supported

What version of the product are you using? 1.3.0-1

On what operating system?
Linux Mint 17

Please provide any additional information below.

Microsoft extensions are enabled and proxytester gives an error that isInNetEx 
is not defined.

Original issue reported on code.google.com by [email protected] on 7 Feb 2015 at 3:23