I'm working on an attachment-solution for my forums which should offload the php-part if it just generates the secure url and the actual check and delivery is done by litespeed without running the file through the php-processes.
Sorry but that gains me exactly nothing .
I have the hit on the php-processes already so I can serve the file by php with no additional hit.
I just want to generate "secured" urls already on the read-page and when these urls are clicked they are directly delivered through litespeed instead of the php-process which would otherwise be called.
Yes, it still hits php, but it will be much efficient than letting php serve the file directly.
The cost of hitting php is higher than handling it inside web server, but the gain is probably too small to be justified a internal module.
Another solution is to write a simple LSAPI application to implement some thing like mod_secdownload + a internal redirect. Should be very close to a internal module performance wise, and you got the flexibility of using any algorithm you want.
Another solution is to write a simple LSAPI application to implement some thing like mod_secdownload + a internal redirect. Should be very close to a internal module performance wise, and you got the flexibility of using any algorithm you want.
Sounds like an interesting approach if I would know anything about the LSAP-protocol and would have refreshed my C/C++ knowledge from years ago .
So, experienced LSAPI-developers speak up, how about such a module?
mod_secdownload equivalent for litespeed?
.
.
Linear Mode
