Support for non-standard ports

5 views
Skip to first unread message

John

unread,
Apr 30, 2008, 3:22:46 PM4/30/08
to pactester
Does pactester handle non-standard ports in URLs, e.g. http://<FQDN>:9001/
?

We have complicated PAC files and pactester has saved us many times.

Thanks, John

Manu Garg

unread,
May 1, 2008, 6:58:44 AM5/1/08
to pact...@googlegroups.com
On Thu, May 1, 2008 at 12:52 AM, John <john...@gmail.com> wrote:
>
> Does pactester handle non-standard ports in URLs, e.g. http://<FQDN>:9001/
> ?

Current release (1.0.7) of pactester handles it correctly only if you
specify both URL and host like this:

./pacptester -p some_pac.wpad -u http://<FQDN>:9001/someurl.html -h FQDN

After your mail I realized that if you specify only URL, then
pactester considers everything between proto :// and / as hostname.
That means port part will go into hostname. This is not in conformance
with the PAC file standard:
http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html

Port number shouldn't be part of hostname. I have just submitted a fix
for it to SVN repository.

You can download modified script from
http://pactester.googlecode.com/svn/trunk/pactester.

I'll include this change in next release.

Thanks for asking for this :)
-Manu
--
Manu Garg
http://www.manugarg.com
"Journey is the destination of life."

John

unread,
May 1, 2008, 1:35:29 PM5/1/08
to pactester
Ah - thanks. Yes, including the "-h" worked. I'll test the enhancement
you've made as well.

- John

On May 1, 4:58 am, "Manu Garg" <manug...@gmail.com> wrote:
> On Thu, May 1, 2008 at 12:52 AM, John <john.p...@gmail.com> wrote:
>
> > Does pactester handle non-standard ports in URLs, e.g. http://<FQDN>:9001/
> > ?
>
> Current release (1.0.7) of pactester handles it correctly only if you
> specify both URL and host like this:
>
> ./pacptester -p some_pac.wpad -u http://<FQDN>:9001/someurl.html -h FQDN
>
> After your mail I realized that if you specify only URL, then
> pactester considers everything between proto :// and / as hostname.
> That means port part will go into hostname. This is not in conformance
> with the PAC file standard:http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html
>
> Port number shouldn't be part of hostname. I have just submitted a fix
> for it to SVN repository.
>
> You can download modified script fromhttp://pactester.googlecode.com/svn/trunk/pactester.
>
> I'll include this change in next release.
>
> Thanks for asking for this :)
> -Manu
> --
> Manu Garghttp://www.manugarg.com
Reply all
Reply to author
Forward
0 new messages