What is particularly different in this case is that this filtering does not
return a 403 Code or TCP RST -- when a GET request for a .mp3 file is sent,
the connection is simply blocked. The server can send whatever it likes,
but the client will not see anymore traffic after that. This is abnormal,
No apparent blockade on anything in Ogg Vorbis formats? In that
instance, /LISTen: An LISNews.org Program/ may still be accessible in
Iran then.
Stephen Michael Kellat, MSLS
Presenter, /LISTen: An LISNews.org Program/
http://lisnews.org/podcast
On 10/06/2012 02:30 PM, Amin Sabeti wrote:
Iran's
On 10/6/12 10:36 PM, Collin Anderson wrote:
File extension in URL requested, Content-Type or are they even finding
their own Content-Type?
You are correct, all that it took to trigger the blocking was a php
file with the following:
header(Content-Type: audio/mpeg);
The server
So maybe, just throwing away the Content-Type header from an HTTP
responses, could still allow the browser to identify/access the data, while
avoiding the Iranian filter to detect it?
That is solid advice, however, I suspect most the streaming media sites
that would pay such special
