#839 repeated error 330 on google search on chromium (using SDCH)

version 3.0.17
closed-fixed
5
2011-03-20
2011-03-19
zebul666
No

using 10.0.648.133 (77742) Ubuntu 10.10 and privoxy 3.0.16 (for ubuntu 10.10 official repo) I got 3 times out of 4 a error 330 when I do a search from the url bar of chromium:

Erreur 330 (net::ERR_CONTENT_DECODING_FAILED) : Erreur inconnue

I found those issue reported on chromium bug tracker:
http://code.google.com/p/chromium/issues/detail?id=24365

this is supposed to be fixed a long time ago in privoxy ??
also trying the mentionned fix
{ -filter }
www.google.com
ggogle.com

had no effect here.

I must say that using chromium 10.0.648.134 and privoxy 3.0.17, I never had such an issue.

Is this an ubuntu bug ? or a bug in privoxy 3.0.16 that has been fixed since ? I see no such bug here.

Discussion

  • Fabian Keil

    Fabian Keil - 2011-03-19

    Thanks a lot for the report.

    There haven't been any changes between 3.0.16 and 3.0.17 with the intention to address compatibility issues with Google's SDCH encoding, otherwise they ChangeLog would mention them.

    Of course it's possible that there has been a change in the past that fixed the problem as an unintended side-effect, but without further details about what exactly the problem is, that's hard to tell.

    Unfortunately Wan-Teh Chang's request for additional information at http://code.google.com/p/chromium/issues/detail?id=21873#c5 has been ignored, otherwise the problem probably would have already been properly diagnosed and forwarded if necessary, just like the NTLM issues have been in the past:
    https://sourceforge.net/tracker/index.php?func=detail&aid=2717882&group_id=11118&atid=111118

    While http://code.google.com/p/chromium/issues/detail?id=24365 and http://code.google.com/p/chromium/issues/detail?id=37777 contain workarounds (and FUD), they are a bit light on technical details.

    Is there a chance that you could reproduce the problem with the debug settings described at:
    http://www.privoxy.org/user-manual/contact.html#CONTACT-BUGS
    and attach a Privoxy log file?

    Be aware of the warning: "Note that Privoxy log files may contain sensitive information so please don't submit any logfiles you didn't read first. You can mask sensitive information as long as it's clear that you removed something."

    If you still can only reproduce the problem with Privoxy 3.0.16, but not with 3.0.17, it would also be useful to get a log for 3.0.17 to compare.

     
  • Fabian Keil

    Fabian Keil - 2011-03-19
    • assigned_to: nobody --> fabiankeil
    • labels: --> funct: filtering
    • status: open --> pending
     
  • zebul666

    zebul666 - 2011-03-19
    • status: pending --> open
     
  • zebul666

    zebul666 - 2011-03-19

    I forgot a word. it works with privoxy 3.0.17 on ARCHLINUX.

    so I enable debug option and got a log for privoxy 3.0.16 but even when compiling privoxy 3.0.17 I was unable to get a log on archlinux (I mean a log with details). I don't know why.

    also the more I tried the less it happended so that now I can't reproduce anymore the error by searching in the url bar !!! but no configuration changed !

    look for qjsshha or jdjdaop+opz+poep+z in the log. that searches failed with error 330

     
  • zebul666

    zebul666 - 2011-03-19

    ok. I got the error back

    using --enable-sdch=never_enable_sdch_for_any_domain seems (I see *seems*) to fix the problem

     
  • Fabian Keil

    Fabian Keil - 2011-03-20
    • milestone: --> version 3.0.17
    • status: open --> pending-accepted
     
  • zebul666

    zebul666 - 2011-03-20
    • status: pending-accepted --> open-accepted
     
  • zebul666

    zebul666 - 2011-03-20

    I can't compile privoxy 3.0.16 with 1.219 parsers.c. it fails with an error

    I have tried a compiled from source (not debian package) 3.0.17 with patched parsers.c on ubuntu. It *seems* to work.
    but then I tried 3.0.17 without the patch and it *seemed* to work too !
    I don't know what to think of that
    also why was it working on archlinux ? compilation option of chromium ?

    non essential matter is:
    on archlinux, I recompiled with --with-debug, and enable debug option in /etc/privoxy/config but did not get any more verbose log in logfile. I used logdir /tmp to get a tmp logfile insttead of the system /var/log/privoxy/logfile

     
  • Fabian Keil

    Fabian Keil - 2011-03-20

    What I meant is that you should be able to apply the patch http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/parsers.c?r1=1.218&r2=1.219&view=patch to the 3.0.16 sources, not that you can replace the whole file.

    To apply the patch, download it, cd into the 3.0.16 source directory and run:
    patch < /path/to/patch-file

    Alternatively you can manually replace the server_content_encoding() function with the one from CVS.

    If logging works with your Privoxy 3.0.16 configuration file, comparing it to the one you use with 3.0.17 would probably help you figure out where the problem is.

    Simply using your Privoxy 3.0.16 configuration with the 3.0.17 binary is likely to work, too.

     
  • Fabian Keil

    Fabian Keil - 2011-03-20
    • status: open-accepted --> pending-accepted
     
  • zebul666

    zebul666 - 2011-03-20

    I have rebuld a privoxy 3.0.16 ubuntu package with the patch.
    so it *seems* to work now. no more error 330

     
  • zebul666

    zebul666 - 2011-03-20
    • status: pending-accepted --> open-accepted
     
  • Fabian Keil

    Fabian Keil - 2011-03-20
    • summary: repeated error 330 on google search on chromium --> repeated error 330 on google search on chromium (using SDCH)
    • status: open-accepted --> closed-fixed
     
  • Fabian Keil

    Fabian Keil - 2011-03-20

    Great. Thanks for the confirmation.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks