tag 490669 + unreproducible moreinfo
thanks

Martin Steigerwald schrieb am Sonntag, den 13. Juli 2008:

Sorry for the delay, I was a little bit inactive with privoxy in the
last weeks...

> Package: privoxy
> Version: 3.0.8-1
> Severity: normal
> 
> Domain matching privoxy does not seem to work as advertised.
> 
> With my current settings privoxy filters out the style sheet of
> http://www.lusc.de
> 
> I didn't want to bother so I just added .lusc.de to fragile in
> user.action using the web interface:
> 
> # Now you noticed that the default configuration breaks Forbes
> # Magazine, but you were too lazy to find out which action is the
> # culprit, and you were again too lazy to give feedback, so you just
> # used the fragile alias on the site, and -- whoa! -- it worked. The
> # 'fragile' aliases disables those actions that are most likely to break
> # a site. Also, good for testing purposes to see if it is Privoxy that
> # is causing the problem or not.
> #
> { fragile }
> .lusc.de
> #.forbes.com
> 
> This works if I use www.lusc.de, but when I use lusc.de instead the CSS
> still is filtered.

Strange.  I tried the same with 

{ +block }
.lusc.de

on a fresh installed privoxy 3.0.8-1 (no modifications except this)
and it blocks all lusc.de stuff without problems:

| Request for blocked URL
| 
| Your request for http://lusc.de/ was blocked.
| See why or go there anyway.

And "See why" shows me:

| In file: user.action View Edit
| {+block }
| .lusc.de

After this I also tried your configuration and when I have a look at
http://config.privoxy.org/show-url-info?url=http%3A//lusc.de/dokuwiki/lib/styles/style.css
it shows me:

| In file: user.action View Edit
| {-block
| -crunch-incoming-cookies
| -crunch-outgoing-cookies
| -fast-redirects
| -filter
| -hide-referrer
| -kill-popups
| -prevent-compression }
| .lusc.de

Which is exactly the "fragile" set.
So it seems, that I cannot reproduce your problem here...

Tschoeeee

        Roland



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to