Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
seahub behind apache with mod_proxy_fcgi does not work #884
I tried to set up seahub behind apache 2.4 with mod_proxy_fcgi instead of mod_fastcgi.
The only difference should be that the apache config does not need the FastCGIExternalServer line and the rewrite rule should look like this:
Notice the P as the last flag.
Obviously apache hands the request to seahub (http://example.com/), as seahub issues a Location header for a redirect to http://example.com/accounts/login. (Notice the missing ending slash, which is present when doing it with mod_fastcgi)
Does anybody have a hint for me, what the correct configuration is, such that I can use mod_proxy_fcgi?
I'm not a python/django programmer, so I've no clue how/where to debug the thing, to find out the subtle difference between these fcgi approaches.
Thanks for your help.
For Seafile 4.0.0, I made it work with the following configuration:
As you can see, there are no rewrite rules at all. The key is setting the proxy-fcgi-pathinfo environment variable. This will make mod_proxy_fcgi pass the path info to the FCGI script (by default it will not). Unfortunately, I could not make the seafdav service work via FCGI (I am getting a Python TypeError exception). I am not sure whether this is a general bug in the 4.0.0 beta release or it is a problem with mod_proxy_fcgi vs. mod_fastcgi. Anyway, it works fine when running in HTTP mode.
added a commit
Mar 23, 2015
referenced this issue
Mar 23, 2015
Hi all, i have a problem to deploy seafile under Apache/mod_proxy_fcgi.