Path: csiph.com!weretis.net!feeder4.news.weretis.net!feeder1.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: Re: Read binary file Date: Thu, 17 Mar 2016 23:15:05 +0100 Organization: PointedEars Software (PES) Lines: 85 Message-ID: <33146564.cWhRoE1DKn@PointedEars.de> References: <145821661.4prVZSFEgG@PointedEars.de> <2237637.9AE1fihV9u@PointedEars.de> <6005521.MME42bj82n@PointedEars.de> Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: solani.org 1458252906 14141 eJwNy8EBwCAIA8CVpDEBxkEq+4/Q3v8Imdq3qM3hqLAAE/pVVPhx5zgtn1RHqJK4xy7/hHXjAwDtEC0= (17 Mar 2016 22:15:06 GMT) X-Complaints-To: abuse@news.solani.org NNTP-Posting-Date: Thu, 17 Mar 2016 22:15:06 +0000 (UTC) User-Agent: KNode/4.14.2 X-User-ID: eJwFwQkBwDAIA0BLg5JQ5JTPv4Td4VBYbgQNi3UiZvpNmkav5uOx/Rj34huMyErVQWZoarm6dT4bOLpE9QdkLRXC Cancel-Lock: sha1:YvaIiQF7BymWiGF2rVUbBXkBJOo= X-NNTP-Posting-Host: eJwFwYEBwCAIA7CXAKV158wC/59gkgsOcSOxc3KcTmp1bMnaYOqoMvkqduHQzl9zdfhdxMQDG+8RXA== Xref: csiph.com comp.lang.javascript:30041 Herbert Kleebauer wrote: > 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 It was trivial to me (I did the configuration – essentially one line in an .htaccess file – of my local server this evening in less than one hour), although I have to admit that I had to look a few things up as I did not remember them exactly (Stack Overflow was very helpful there as other people faced the same, eventually trivially-to-solve, problems as I). > nor a solution at all. Have you even tried it? > 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. They do not have to. As you are reading superficially, you are jumping to conclusions. > I can understand why a server doesn't deliver the picture if it doesn't > like a referer header, That is the only catch with the solution I suggested (and *tried* *successfully*) that I can think of. If the Referer [sic!] header field value is checked by the original host, then either the user must disable transmitting that header field in their browser, or the forward proxy must be configured not to forward that header field (assuming that the original host is not unwisely configured to depend on the transmission of that field, since it is optional according to HTTP). It may also be necessary for the forward proxy to pretend to be a (certain) Web browser by sending corresponding header fields (at least, “User-Agent”). > 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). You have not even attempted to google “Same Origin Policy” yet, have you? It is futile to complain about this (here). Browsers work the way that they do. All you can do is make the best of it since not all of those that are used are free software. >>>> There is no javascript. >>> ??????????? >> See the reference to the “ES Matrix” in my signature. > > jpg > When I said “See the reference …”, I meant that you should *follow* the reference and *read* the explanations in the referred document. I did not mean that you should post code in order to support your misconceptions. > It is declared as javascript It is not. > and therefore it is by definition javascript. Ex falso quodlibet. > Whether it is processed by a javascript, JavaScript or a ECMAScript > interpreter doesn't matter, by definition the code itself is javascript > code. Such a nonsense, it is not even wrong. -- PointedEars FAQ: | SVN: Twitter: @PointedEars2 | ES Matrix: Please do not cc me. / Bitte keine Kopien per E-Mail.