[ ijbswa-Actionsfile feedback-3614694 ] Instagram broken?
SourceForge.net <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
Actionsfile feedback item #3614694, was opened at 2013-07-12 18:56
Message generated for change (Comment added) made by mrahk
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=460288&aid=3614694&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: filter: other problem
Group: None
>Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: mrahk (mrahk)
Assigned to: Fabian Keil (fabiankeil)
Summary: Instagram broken?
Initial Comment:
Until recently Instagram was playing well with Privoxy but apparently something has changed.
Let's take for example this url:
http://instagram.com/p/brEENnvs5Y
I can't make the big picture in the left pane appear unless I completely bypass Privoxy.
I've tried it with fragile and disabling every kind of filtering I could reasonably think of but nothing seems to work.
----------------------------------------------------------------------
>Comment By: mrahk (mrahk)
Date: 2013-07-13 08:34
Message:
No, I did not try it with a default configuration and that is of course the
source of the trouble.
In the meantime I've found out what's wrong.
The tricky js-events filter needs definitely to be disabled for
.cloudfront.net.
And there was some trouble with a self created filter group to get rid of
some social media stuff, web bugs and webcounters not yet covered by the
standard filters of Privoxy.
Apparently one of those filters is a bit overzealous.
B.T.W.: Do you have a method to find out which rule fired without setting a
ridiculous amount of { +filter{something} } tags?
B.T.W.2: Thanks for the time you've invested in this issue and for sharing
Privoxy with us all.
----------------------------------------------------------------------
Comment By: Fabian Keil (fabiankeil)
Date: 2013-07-13 06:10
Message:
I can't reproduce this. Did you try it with a default Privoxy
configuration?
If you have, please reproduce the problem with logging enabled and attach a
log excerpt:
http://www.privoxy.org/user-manual/contact.html#CONTACT-BUGS
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=460288&aid=3614694&group_id=11118
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk