<div dir="ltr">Correct. My apologies.<div><br></div><div>It's not HTTP that is blocked. Not sure what is at this stage but thanks for the help.</div><div class="gmail_extra"><br><div class="gmail_quote">On 28 September 2015 at 09:33, Amos Jeffries <span dir="ltr"><<a href="mailto:squid3@treenet.co.nz" target="_blank">squid3@treenet.co.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 28/09/2015 9:12 a.m., Yuri Voinov wrote:<br>
><br>
> It not seems blocked.<br>
><br>
> Blocked URL has TCP_DENIED tag.<br>
><br>
<br>
Unless the media portion is not even using HTTP. The problem would then<br>
be somewhere else outside Squid.<br>
<br>
<br>
> 28.09.15 1:54, Henry McLaughlin пишет:<br>
>>><br>
>>> On 27 September 2015 at 17:07, Henry McLaughlin wrote:<br>
>>><br>
>>>> I am having problems using a radio streaming application on my<br>
> phone. The<br>
>>>> phone connection is routed via squid proxy server. If I by pass<br>
> squid then<br>
>>>> the radio application works. The application is TuneIn radio<br>
> (<a href="http://tunein.com" rel="noreferrer" target="_blank">tunein.com</a>).<br>
>>>> I have read a number of posts regarding blocking streaming services<br>
> however<br>
>>>> have not found how to unblock one as I suspect the service is blocked by<br>
>>>> default.<br>
>>>><br>
>>>> The following appears in the access log:<br>
>>>> 1443337149.538 3239 192.168.1.102 TCP_MISS/200 653 GET<br>
>>>> <a href="http://ads.tunein.com/creatives" rel="noreferrer" target="_blank">http://ads.tunein.com/creatives</a>? - HIER_DIRECT/<a href="http://176.34.44.113" rel="noreferrer" target="_blank">176.34.44.113</a><br>
>>>> application/json<br>
>>>> 1443337151.830 1968 192.168.1.102 TCP_MISS/200 6367 GET<br>
>>>> <a href="http://ads.mopub.com/m/ad" rel="noreferrer" target="_blank">http://ads.mopub.com/m/ad</a>? - HIER_DIRECT/<a href="http://192.44.68.3" rel="noreferrer" target="_blank">192.44.68.3</a> text/html<br>
>>>> 1443337152.292 3661 192.168.1.102 TCP_MISS/200 478 GET<br>
>>>> <a href="http://opml.radiotime.com/Report.ashx" rel="noreferrer" target="_blank">http://opml.radiotime.com/Report.ashx</a>? - HIER_DIRECT/<a href="http://204.69.221.89" rel="noreferrer" target="_blank">204.69.221.89</a><br>
>>>> text/xml<br>
>>>> 1443337152.355 4029 192.168.1.102 TCP_MISS_ABORTED/200 3250 GET<br>
>>>> <a href="http://67.212.174.228:10001/" rel="noreferrer" target="_blank">http://67.212.174.228:10001/</a> - HIER_DIRECT/<a href="http://67.212.174.228" rel="noreferrer" target="_blank">67.212.174.228</a> audio/mpeg<br>
<br>
<br>
The only problem in this log seems to be the request above. Which is<br>
apparently successfully getting put through to the required server, but<br>
the client aborts it after 4 seconds with only a tiny/3KB amount of<br>
response getting back.<br>
<br>
When I try it myself I get an ICY stream back. Squid does support those.<br>
At least 3.1 and later do, if you are using an older Squid you *really*<br>
need to upgrade.<br>
<br>
<br>
<br>
There is a chance that your ISP or some device upstream is blocking the<br>
traffic. Since its aparently getting the response, but not much I<br>
suspect MTU issues somewhere. The HTTP reply headers would get through<br>
as small packets, but the media itself may need large ones that get dropped.<br>
<br>
<br>
There is a huge amount of advertising being thrown at the client. It<br>
might be spending all its time processing that and not get around to the<br>
actual content you want. Try adding this to squid.conf to eliminate that<br>
and see if things work better:<br>
<br>
acl ads dstdomain <a href="http://ads-bidder-api.twitter.com" rel="noreferrer" target="_blank">ads-bidder-api.twitter.com</a> \<br>
.<a href="http://google-analytics.com" rel="noreferrer" target="_blank">google-analytics.com</a> <a href="http://ads.tunein.com" rel="noreferrer" target="_blank">ads.tunein.com</a> <a href="http://ads.mopub.com" rel="noreferrer" target="_blank">ads.mopub.com</a><br>
http_access deny ads<br>
<br>
<br>
The site also has a bunch of HTTP violations:<br>
<br>
* Pragma: no-cache is a request directive, not a response directive.<br>
* A ranged request returned another representation.<br>
* The X-XSS-Protection header's syntax isn't valid.<br>
* Response is negotiated, but doesn't have an appropriate Vary header.<br>
* The resource doesn't send Vary consistently.<br>
<br>
While these are only from the web pages and images of the site they are<br>
bad signs about the developers abilities.<br>
<br>
Amos<br>
_______________________________________________<br>
squid-users mailing list<br>
<a href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
<a href="http://lists.squid-cache.org/listinfo/squid-users" rel="noreferrer" target="_blank">http://lists.squid-cache.org/listinfo/squid-users</a><br>
</blockquote></div><br></div></div>