phusion
Support for mod_userdir
From benabik on April 22, 2008 18:46:57
Using passenger on the root of a web server prevents userdir requests (such as ~user) from being handled properly. Ideally, Passenger should allow mod_userdir to handle requests before attempting to send them to the rails application.
Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=33
From honglilai on April 22, 2008 10:10:51
Summary: mod_userdir is incompatible (Passenger ignores mod_userdir)
Labels: ConflictingModule
From benabik on June 17, 2008 11:13:39
Is this issue solved in Passenger 2.0-rc1? This is blocking my deployment of passenger.
From benabik on February 04, 2009 00:20:06
I've written a basic patch that seems to allow mod_userdir to handle requests intended for it by simply ignoring things that look like userdir requests when the Passenger app is running from / and mod_userdir is loaded.
This at least seems like the right place to start. I couldn't find a way to tell if mod_userdir was enabled, only if it was loaded. Nor does it attempt to validate the userdir call at all, so requests like /~invalid_user get the standard Apache 404 page instead of the application 404.
I also did not test if Passenger applications inside a userdir worked. However, I don't believe they worked previously so this at least isn't a regression.
Attachment: 0001-Ignore-requests-for-mod_userdir.patch
From jphpsf on September 15, 2010 08:57:59
Resolving this would be really useful.
For now, I am deploying multiple apps under DocumentRoot of Apache. I will probably try the mass deployment feature from passenger 3 soon and have it point to ~/public_html
Damn, I'm totally not familiar with such code but totally would love to help out but would not know where to start to be honest! It's just really sad now that cPanel released their own native NodeJS apptm that relies on this module but many webhost also use the other mod that I mentioned, especially shared... I was really really looking forward for this and it's quite the letdown not only for this not being compatible but also from my host not even trying to find a different solution other than saying they're not compatible.
Could I ask where it exactly does conflict maybe I could look into it and learn while I look into it!
This at least seems like the right place to start. I couldn't find a way to tell if mod_userdir was enabled, only if it was loaded. Nor does it attempt to validate the userdir call at all, so requests like /~invalid_user get the standard Apache 404 page instead of the application 404.
Updating the patch to apply cleanly to the current codebase as well as answering the questions @FooBarWidget still had last he looked at this would be the next steps here.