search

binarycrusader / libproxy

Automatically exported from code.google.com/p/libproxy
GNU Lesser General Public License v2.1
0 stars 0 forks source link

the process "proxy" is not looking for wpad.dat file #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Execute the sample program "proxy".
2. Monitor HTTP traffic for that process.
3. There is no request for WPAD file from the host.

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

If I set "Auto Detect Proxy Settings" in Firefox, then whenever I start FF 
there will be a request for the wpad.dat file from FF.
But there is no such request going from the process "proxy".

OS: Windows Vista.
Product version: revision 550 in trunk

Original issue reported on code.google.com by ruj.sa...@gmail.com on 15 Feb 2010 at 10:38

GoogleCodeExporter commented 9 years ago 
Also, the sample program is saying proxy is "direct://", whereas FF is fetching 
the 
wpad.dat file and working through proxy.

Original comment by ruj.sa...@gmail.com on 15 Feb 2010 at 10:40

GoogleCodeExporter commented 9 years ago 
Can  you provide me a screen-shot of the "LAN settings" dialog which shows your
current configuration?

Original comment by npmccallum@gmail.com on 15 Feb 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
1) It should not matter. Because if I am writing a program which has a option 
"Auto 
detect proxy settings", like Firefox does, then I should be calling the 
"px_proxy_factory_get_proxies" function. So, it is irrelevant what is set in 
the LAN 
settings. The applications can have an option like "Auto detect proxy settings".

2) Anyway I have attached the screenshot.

Original comment by ruj.sa...@gmail.com on 16 Feb 2010 at 7:33

Attachments:

GoogleCodeExporter commented 9 years ago 
1. Your program should not provide proxy settings.  It should rely on the global
system's proxy settings.  This is what libproxy uses.  Providing per-application
proxy settings is beyond the scope of libproxy.

2. Ok, your configuration is correct.  Let me do some testing to see if there 
is a bug.

Original comment by npmccallum@gmail.com on 16 Feb 2010 at 2:27

GoogleCodeExporter commented 9 years ago

Original comment by npmccallum@gmail.com on 17 Feb 2010 at 2:07

GoogleCodeExporter commented 9 years ago 
This should be fixed now.  Please try the latest trunk.

Original comment by npmccallum@gmail.com on 22 Feb 2010 at 10:52