This module extends drupal private files downloads to use
http://www.cherokee-project.com/doc/modules_handlers_secdownload.html
* Links created for private files expire after a defined time.
* Serving private files is offloaded to the server if configured (X-Sendfile ...)
PHP:
Default delivery using just php mechanisms. Should work on all servers.
X-Sendfile X-Accel-Redirect:
Checks are done in PHP and the download offloaded to the server if supported.
Server:
Offload checks and download to server.
Comments
Comment #1
gregglesCan you post a link to your sandbox?
Comment #2
wienczny commentedAh sorry here it is: http://drupal.org/sandbox/wienczny/1146078
Comment #3
gregglesComment #4
ralt commentedChanging priority according to the new priority guidelines.
Comment #5
mlncn commentedThese lines should be removed:
Now files directive is only used for additional includes that have classes.
Hook-implementing functions should always be introduced with the comment line "Implements hook..."
Check on coding standards in general.
Apologies for the ridiculous delay.
Comment #6
misc commentedThe applicant has been contacted to ask if the application is abandoned.
Comment #7
wienczny commentedI hope to have fixed all issues in #5 with commit 1e6c8ba
The module is not abandoned. The notification about #5 just got lost between drupal security ones ;-)
Comment #8
misc commentedGreat!
You have a couple of coding standards issues:
http://ventral.org/pareview/httpgitdrupalorgsandboxwienczny1146078git
In the README.txt lines should not exceeds 80 characters (that is also for comments in module files)
The second line in the file doc comment must be " * @file", like:
All functions should have comments, like (dummy example):
Mostly of the warnings is about indenting - so is should be pretty easy ti fix.
You could do a new automatic review yourself if you reuse the url above.
If you have any questions, please ask, so hopefully the process is going to be quick.
Comment #9
wienczny commentedI changed the files and pareview does not find anything, now.
http://ventral.org/pareview/httpgitdrupalorgsandboxwienczny1146078git
The comments were already there and were just reformatted. pareview should give some nicer message if the file comment is not at the correct position. It started in line 3 instead of 2 and the message was "File comment missing"
Comment #10
thursday_bw commentedAs per the pareview output. You are working in the master branch.. You should have only a README.txt file in your master branch and work in a 7.x-1.x branch.
see documentation:
Comment #11
thursday_bw commentedComment #12
wienczny commentedMoved to 7.x-1.x branch.
Comment #13
themebrain commentedReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
Source: http://ventral.org/pareview - PAReview.sh online service
Manual review:
- Should use t function with title and description for example:
- Should use drupal_realpath here:
Comment #14
wienczny commentedHi I fixed the problem with the path. I'm directly using the wrapper now.
The documentation says title and description in hook_menu must not be translated: See "title callback" in hook_menu
Comment #15
jthorson commentedStill some 'dot' files in your master branch, which should be cleared out.
Otherwise, a quick scan looks good ... I don't pretend to understand how cherokee hidden downloads work, but I think it's safe to assume you do. ;)
Comment #16
wienczny commentedIt's not just a feature of cherokee. Nginx has something like that, too http://wiki.nginx.org/HttpSecureLinkModule They use a different url scheme. A feature for a future version if somebody needs it.
Comment #17
klausimanual review:
Comment #18
wienczny commentedI'll update the project page in the next days.
A new access permission was added.
drupal_exit is used instead of exit now. I was not aware that drupal_exit guarantees not output by other modules .
I don't agree on the the use of !=. You could argue to use !==, so. There were old php-Versions where strings could be php- or c-style and when compared to each other were not identical. I can't reproduce this with my current php-Version so it must be gone.
Comment #19
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.