sunzhenguo / pacparser

Automatically exported from code.google.com/p/pacparser
GNU Lesser General Public License v3.0
0 stars 0 forks source link

PAC Files with myIpAddress() used seem to cause a reference error #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use included myip.dat as input for the pacparser test sample
2. The dat file as all lines commented out apart from the one with myIpAddress()

What is the expected output? What do you see instead?

Expected output - a valid proxy as returned by the file.

Returned output - 

  JSERROR: c:\myip.dat:11:
    ReferenceError: myIpAddress is not defined

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

pacparser 1.0.3, Windows 2003 Server, Visual Studio 2003.

Please provide any additional information below.

I have tried almost all the different types of pac files that can be found on 
the internet. This 
seems to be the only function that gives a problem. 

I am not sure how prevelant usage of myIpAddress() is, but would be a nice 
addition to the 
library.

Original issue reported on code.google.com by nbharatv...@gmail.com on 14 Apr 2008 at 12:11

Attachments:

GoogleCodeExporter commented 9 years ago
This looks like a Windows specific error as you pac file works perfectly fine 
on Linux:

manugarg@hobbiton:~/Desktop$ python -c 'import pacparser; print
pacparser.just_find_proxy("myip.dat", "http://www.google.com")'
DIRECT

I don't have access to a Windows system right now. I'll take a look at it soon.

Original comment by manugarg on 14 Apr 2008 at 2:11

GoogleCodeExporter commented 9 years ago

Original comment by manugarg on 14 Apr 2008 at 2:40

GoogleCodeExporter commented 9 years ago
This issue has been fixed in the latest version in repository. For changes 
details:

http://code.google.com/p/pacparser/source/detail?r=62

Original comment by manugarg on 17 Apr 2008 at 10:13

GoogleCodeExporter commented 9 years ago
This issue has been fixed in the new release of pacparser: 1.0.4. Please look 
at the
changelog for more details about the release.

Thanks nbharatvarma for reporting this issue :)

Original comment by manugarg on 18 Apr 2008 at 7:39