Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Herbert Kleebauer Newsgroups: comp.lang.javascript Subject: Re: Read binary file Date: Thu, 17 Mar 2016 22:36:13 +0100 Organization: Aioe.org NNTP Server Lines: 33 Message-ID: References: <145821661.4prVZSFEgG@PointedEars.de> <2237637.9AE1fihV9u@PointedEars.de> <6005521.MME42bj82n@PointedEars.de> NNTP-Posting-Host: eiWAGHWzYgT9obq29hja2A.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.javascript:30040 On 17.03.2016 21:43, Thomas 'PointedEars' Lahn wrote: > Stefan Weiss wrote: >> So, now that the copyright situation has been explained, what's the >> trivial solution? > Transparent HTTP proxying with mod_rewrite, mod_proxy, mod_proxy_http & That's neither a trivial solution nor a solution at all. The user only gets the the url of the original picture and the url of the modifcation file. The user doesn't use a proxy. I can understand why a server doesn't deliver the picture if it doesn't like a referer header, but I can't understand the restrictions by the browser. I see it as a fundamental function to read any accessible file on any web server into a javascript array (even by removing the referer header if necessary). >>> There is no javascript. >> ??????????? > See the reference to the “ES Matrix” in my signature. jpg It is declared as javascript and therefore it is by definition javascript. Whether it is processed by a javascript, JavaScript or a ECMAScript interpreter doesn't matter, by definition the code itself is javascript code.