What Martin describes in the wiki.
That is actually a grave security bug. So the default templates should be modified to not have the modproxy circumvent WebGUI's security.
Koen de Jonge - ProcoliXhttp://www.procolix.comHosting - WebGUI - Virtualization
This is set this way on purpose. It is simple to change for people that need it, but imposes severe performance issues.
This isn't going to be changed. Documentation could be changed if needed though.
What do you mean by "severe performance issues"? The request is still being handled by Apache albeit the modperl instance instead of the light-weight modproxy. Please elaborate.
William
----Knowmad Technologieshttp://www.knowmad.com
I may have overstated the performance drawbacks, but there is still a lot more processing that has to be done to have modperl handle uploads. JT explained the difference in the process on the dev mailing list. If you have a large number of images used in your pages, you could start to see slowdowns on your site.
I've added a note about this to the WRE's modproxy template. Any other recommendations for documentation changes are welcome.
