Is reverse proxy considered as a form of “public mirror”?
<p>The Anaconda repo states that:</p>

<blockquote>
  <p>Public mirrors of this are not allowed without express permission from Anaconda, Inc.</p>
</blockquote>

<p>If someone builds a public reverse proxy to <a href="https://repo.continuum.io/pkgs/" rel="nofollow noreferrer">https://repo.continuum.io/pkgs/</a> , is it considered as a violation of terms above?</p>

<p>A reverse proxy is a service that does not store upstream packages on a local disk like a mirror server, instead, every time a user requests a package from reverse proxy, the proxy server fetches it just in time from upstream and send it back to the user. From the users perspective, it behaves just like a mirror with more delays. However, reverse proxy is also broadly used in public networks.</p>

<p>For more details, <a href="https://opensource.stackexchange.com/questions/4471/agpl-violation-using-reverse-proxy">https://opensource.stackexchange.com/questions/4471/agpl-violation-using-reverse-proxy</a> is probably a good explanation.</p>

<p>To be considered a "public mirror", a service would need to store and make available the same files that are upstream, thus mirroring the files. </p>

<p>A reverse proxy is just another point to access where the files are stored but doesn't actually store any files. </p>

internet intellectual-property licensing