Menu

#1417 Inconsistent output between IE8/IE9?

3.0.17
closed
blocking (193)
5
2011-04-23
2011-04-22
No

I just installed v3.0.17 on two machines: Win7 64bit with IE9 and Vista 32bit with IE8. I enabled Privoxy's log (debug 1024) but otherwise I'm using the default config on both pcs.

Selecting various torrent files on btjunkie.org, on the IE9 machine I get "Crunch: Blocked: http://static.btjunkie.org/adserve.php?zone=bottom&user_type=ros" in the log, and the web page says "Request blocked by Privoxy: Catch-all block for false-positives..." in place of an ad. On the IE8 machine I get the identical log message, but the web page just shows a blank area with a small gray blob in the upper-left corner in place of the ad. Why is the IE8 machine giving me less information... could it be the browser version?

Discussion

  • Fabian Keil

    Fabian Keil - 2011-04-23
    • milestone: --> 3.0.17
    • assigned_to: nobody --> fabiankeil
    • status: open --> pending
     
  • Fabian Keil

    Fabian Keil - 2011-04-23

    Privoxy's default configuration uses various heuristics to guess what kind of
    format the browser is expecting.

    In case of an iframe tag it's not that important, but if the request is made for
    an img tag the browser will most-likely not be able to deal with non-image
    content.

    If the request looks like an image request (because of the URL or the
    client headers), the handle-as-image action is enabled:
    http://www.privoxy.org/user-manual/actions-file.html#HANDLE-AS-IMAGE

    If you increase the debug level to include the headers, you will probably
    see that the requests from IE8 and IE9 look a bit differently.

    You could than add an exception for the requested URL and have Privoxy
    block the request with the "Request blocked ..." message.

     
  • Anonymous

    Anonymous - 2011-04-23
    • status: pending --> closed
     
  • Anonymous

    Anonymous - 2011-04-23

    The headers definitely look different, so it is browser-dependent. I've seen this difference in action on many websites, so it's not worthwhile to create exceptions, When I get more time I'll use the IE developer tools and try various combos of browser mode, document mode and user-agent to see how they affect these GETs. Thanks for the helpful explanation.

     

Log in to post a comment.