Menu
▾
▴
[privoxy-devel] [ ijbswa-Bugs-3433763 ] Different filtering between opperating systems
|
From: SourceForge.net <no...@so...> - 2011-11-07 18:44:16
|
Bugs item #3433763, was opened at 2011-11-04 21:42 Message generated for change (Comment added) made by fabiankeil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=3433763&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: windows-specific Group: version 3.0.17 >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Mathew Murphy (mat75man) Assigned to: Fabian Keil (fabiankeil) Summary: Different filtering between opperating systems Initial Comment: Filtering between OS/2 version 3.0.16 and windows 3.0.16 or .17 is not the same. When I use OS/2 to filter "a action file" .suggestqueries.google.com and suggestqueries.google.com and clients*.google. it works filtering out Google popping up suggestion and auto search. Using the same lines and files Windows version do not filter at all, not even a mention a log file or screen. Thanks for your time. ---------------------------------------------------------------------- >Comment By: Fabian Keil (fabiankeil) Date: 2011-11-07 10:44 Message: Now I'm confused. Both 64logfile.win and 64logfile.os2 show that a google-analytics is executed for several requests but doesn't hit anything. Given that the pages (at least when I request them) don't contain any references to google analytics, that seems reasonable to me. Is the filter supposed to filter something else? It's interesting that 64logfile.os2 shows one response that can't be filtered because it's compressed even though it shouldn't be. This could indicate a misconfigured proxy between Privoxy and the internet. It should only be a problem for the Privoxy version on OS/2 compiled without zlib support though, and not for the Privoxy version on Windows which has. ---------------------------------------------------------------------- Comment By: Mathew Murphy (mat75man) Date: 2011-11-07 00:18 Message: Privoxy logfile for windows and os2 with debug 64 turned on as well as other selected debug settings. With squid I used the debug line " debug_options ALL, 1 " but not sure if the information is any better. Thanks ---------------------------------------------------------------------- Comment By: Fabian Keil (fabiankeil) Date: 2011-11-05 11:47 Message: I can't see any obvious issues in the log files. Please additionally enable "debug 64" so filter execution is logged as well. If using Squid somehow affects the problem, a log for Squid would be useful, too. You also may want to verify that http://config.privoxy.org/show-version actually shows that the page should be filtered. Maybe filtering was previously disabled and your action file change enabled it again. Note that ".google.com.au/extern_*/*/*.*" can be reduced to ".google.com.au/extern" so I'm not sure if that's what you intended. ---------------------------------------------------------------------- Comment By: Mathew Murphy (mat75man) Date: 2011-11-05 05:44 Message: I have fixed it by adding " .google.com.au/extern_*/*/*.* " to a action file, still can't think what Squid has or is doing to over come this. ---------------------------------------------------------------------- Comment By: Mathew Murphy (mat75man) Date: 2011-11-05 05:01 Message: I have found that on my os2 computer "server" using Squid and Privoxy it works, take away Squid and it's not working. Nothing to do with Privoxy and Windows "by them self", sorry about that. I have sent you the files for you to have a look at, would like to hear any thoughts if any you may have. Many thanks. ---------------------------------------------------------------------- Comment By: Fabian Keil (fabiankeil) Date: 2011-11-05 03:29 Message: Thanks for the report. Please reproduce the problem with logging enabled as described at: http://www.privoxy.org/user-manual/contact.html#CONTACT-BUGS and attach the logfile. If logging is enabled and Privoxy still doesn't log anything, there's a fair chance that the client isn't actually using Privoxy. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=3433763&group_id=11118 |