The mailing list for listmasters using Sympa

[Edward Kovarski <address@concealed>]

I have solved the issue for the time being by using the following  
nginx configuration,

        location / {
            fastcgi_pass   127.0.0.1:9090;
            fastcgi_param  QUERY_STRING       $query_string;
            fastcgi_param  REQUEST_METHOD     $request_method;
            fastcgi_param  CONTENT_TYPE       $content_type;
            fastcgi_param  CONTENT_LENGTH     $content_length;
            fastcgi_param  PATH_INFO          $fastcgi_script_name;
        }

It appears that wwsympa does not like SCRIPT_NAME and PATH_INFO  
passed concurrently with nginx.

Initially I was just experimenting with passing either PATH_INFO or  
SCRIPT_NAME but neither seemed to work so looking through the code I  
realized that REQUEST_METHOD needs to get set as well as otherwise  
wwsympa never executes the code that parses the actions. Not sure if  
this breaks anything else but at least it allows me now to further  
evaluate the product.

Note: I re-keyed the URL for Sympa to run from the root (/)  
directory. Not sure if this will also work with /sympa being the home  
directory.


On 19-Sep-07, at 5:05 PM, <address@concealed>  
<address@concealed> wrote:

> Hi,
>
> I am currently evaluating Sympa (5.3.3) but it seems like I've ran  
> into an
> issue using it with nginx and FastCGI.
>
> The issue I've run into appears to be related to how wwsympa parses  
> path_cgi. I
> have Sympa installed under my.host.com/sympa and when I try to  
> access the home
> page the path_cgi and path_info get set to '/sympa' which in turn gets
> interpreted as an 'action' of 'sympa' which does not exist.
>
> Are there any tips and tricks to make Sympa run with nginx or other  
> webservers
> using FastCGI when it has to live under a sublink, e.g. my.host.com/ 
> sympa?