[squid-users] How to block www.infobae.com

[Amos Jeffries]

On 26/11/2016 1:34 a.m., chcs wrote:
> I did it all changes, but again, doesnt works out. Please anybody, can test
> this domain (www.infobae.com) for me?.


Somebody else testing a third-pary site is not the answer to something
on your network being broken.

This is what redbot.org says about the sites use of HTTP:

"
http://www.infobae.com/
Test Duration: 1.29 seconds

    HTTP/1.1 301 Moved Permanently
    Server: AkamaiGHost
    Content-Length: 0
    Location: http://www.infobae.com/america/
    Cache-Control: max-age=600
    Expires: Fri, 25 Nov 2016 14:16:49 GMT
    Date: Fri, 25 Nov 2016 14:06:49 GMT
    Connection: keep-alive

response headers: 242 bytes
body: 0 bytes

General

    The server's clock is correct.
    The Content-Length header is correct.

Caching

    This response allows all caches to store it.
    This response is fresh until 10 min from now.
    This response may still be served by a cache once it becomes stale.
"

"
http://www.infobae.com/america/
Test Duration: 3.84 seconds

    HTTP/1.1 200 OK
    Content-Type: text/html;charset=UTF-8
    PB-PID: pRlMUk1Ja4JZMp
    PB-RID: rBqRuq1L7ZGz3q
    Server: nginx/1.10.1
    Cache-Control: max-age=600, s-maxage=60
    Expires: Fri, 25 Nov 2016 14:18:31 GMT
    Date: Fri, 25 Nov 2016 14:08:31 GMT
    Transfer-Encoding:  chunked
    Connection: keep-alive
    Connection: Transfer-Encoding

response headers: 326 bytes
body: 142,853 bytes
transfer overhead: 70 bytes

General

    The server's clock is correct.

Content Negotiation (Content Negotiation response )

**  The resource doesn't send Vary consistently.
**  The response body is different when content negotiation happens.
    Content negotiation for gzip compression is supported, saving 85%.

Caching

    This response allows all caches to store it.
    This response is fresh until 1 min from now.
    This response cannot be served by a shared cache once it becomes stale.
"

Amos