On 01/04/2011 09:57 AM, Roan Kattouw wrote:
The separate img_auth.php entry point is needed on
wikis where reading
is restricted (private wiis), and img_auth.php will check for read
permissions before it outputs the file. The difference between the
proxy I wrote and img_auth.php is that img_auth.php just streams the
file from the filesystem (which, on WMF, will hit NFS every time,
which is bad) whereas ApiSVGProxy uses an HTTP request (which will hit
the image Squids, which is good).
So ... it would be good to think about moving things like img_auth.php
and thumb.php over to an general purpose api media serving module no?
This would help standardise how media serving is "extended", reduce
extra entry points and as you point out above let us use more uniformly
proxy our back-end data access over HTTP to hit the squids instead of
NFS where possible.
And as a shout out to Trevors mediawiki 2.0 vission, eventually enable
more REST like interfaces within mediaWiki media handing.
--michael