Summary | Replace vfs-direct with X-Sendfile support |
Queue | Ansel |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | mrubinsk (at) horde (dot) org |
Created | 03/09/2008 (6329 days ago) |
Due | |
Updated | 05/21/2008 (6256 days ago) |
Assigned | 03/15/2008 (6323 days ago) |
Resolved | 05/21/2008 (6256 days ago) |
Milestone | |
Patch | No |
State ⇒ Resolved
Assigned to Michael Rubinsky
Taken from Chuck Hagenbuch
for use with x-sendfile. With the file backend it'll just return the
local filename - a much cleaner solution for vfs-direct that should be
just about as fast.
Assigned to Chuck Hagenbuch
State ⇒ Assigned
support this...
you can kick it back to me if I am mistaken :)
addition to the X-Sendfile, for those sites that are OK with the
photos being accessible without permissions checking.
If not, I don't feel strongly about it. It was just a thought.
shortcircuit permission checking even better, but at the moment
permissions aren't checked at all. I don't know if we deem security by
obscurity through hard to guess path/file names sufficient.
those sites that are OK with allowing it? For Ansel, at least, it
would save having to load an Ansel_Image object from the database just
to get the VFS path to send with X-Sendfile header...
it's more efficient to get a local file out of the VFS - with the FTP
backend, for example.
I have some ideas on API changes to VFS for this and then
BC-compatible ways to use them in Ansel, Gollem, maybe IMP too.
State ⇒ Accepted
Priority ⇒ 1. Low
State ⇒ New
Queue ⇒ Ansel
Summary ⇒ Replace vfs-direct with X-Sendfile support
Type ⇒ Enhancement
How about deprecating vfs-direct in Ansel for X-Sendfile support?
http://tn123.ath.cx/mod_xsendfile/
Works with both Apache and Lighttpd, fixes the permissions problem,
and the admins don't have to do much more configuration than with the
vfs-direct feature.