Skip to Content.
Sympa Menu

en - [sympa-users] Re:Wwsympa problems on Debian etch

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: <address@concealed>
  • To: address@concealed
  • Subject: [sympa-users] Re:Wwsympa problems on Debian etch
  • Date: Thu, 24 May 2007 18:30:51 +0200


Olivier,
thanks for your prompt and accurate answer. Let's go step by step:

1. CSS Problem:
> you check the page sources, you'll see that the CSS URL is
> http:///css/style.css, which seems incorrect. This link is defined by
> the 'css_url' sympa.conf URL ; it might be incorrect. If css_url
> parameter is not defined, then the default value is based on the
> 'static_cintent_url' parameter : $static_content_url/css.

I am a little confused here. I thought that static pages were introduced in
Sympa 5.3, not in sympa 5.2.3. I checked for style.css files in my system and
I
found some, but none related to Sympa. So, what address should I provide in
'css_url' option?, and where do I got the files ?

2. Apache VARIABLES
> All links are constructed as follows : $base_url+$path_cgi+... where
> $base_url is based on the HTTP_HOST variable provided by Apache and
> $path_cgi is based on the PATH_INFO environment variable provided by Apache.
>
> It sounds like your Apache does not provide HTTP_HOST and PATH_INFO.
> Misconfiguration ? Proxy mode ?...

Here things seem to be more complicated. I created a perl program that prints
out all variables received by the server, and put it in place of wwsympa.fcgi.
If wwsympa.fcgi is called "directly", the received variables are as follows:
SCRIPT_NAME --> /wws
SERVER_NAME --> www.isebi.org
SERVER_ADMIN --> webmaster@localhost
HTTP_ACCEPT_ENCODING --> gzip, deflate
HTTP_CONNECTION --> Keep-Alive
REQUEST_METHOD --> GET
HTTP_ACCEPT --> image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-
powerpoint, application/msword, */*
SCRIPT_FILENAME --> /usr/lib/cgi-bin/sympa/wwsympa.fcgi
HTTP_UA_CPU --> x86
SERVER_SOFTWARE --> Apache/2.2.3 (Debian) mod_python/3.2.10 Python/2.4.4
PHP/4.4.4-8+etch3 mod_perl/2.0.2 Perl/v5.8.8
QUERY_STRING -->
REMOTE_PORT --> 2047
HTTP_USER_AGENT --> Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1;
InfoPath.1)
SERVER_PORT --> 80
SERVER_SIGNATURE --> Apache/2.2.3 (Debian) mod_python/3.2.10 Python /2.4.4
PHP/4.4.4-8+etch3 mod_perl/2.0.2 Perl/v5.8.8 Server at www.isebi.org Port 80
HTTP_ACCEPT_LANGUAGE --> es-es
REMOTE_ADDR --> 147.83.49.30
SERVER_PROTOCOL --> HTTP/1.1
PATH --> /usr/local/bin:/usr/bin:/bin
REQUEST_URI --> /wws
GATEWAY_INTERFACE --> CGI/1.1
SERVER_ADDR --> 147.83.49.237
REMOTE_HOST --> apofis.upc.es
DOCUMENT_ROOT --> /var/www/
HTTP_HOST --> www.isebi.org
----
As you can see, HTTP_HOST is set to the correct value, but PATH_INFO is not
present. However, because wwsympa (the real one) must be run with
"sympa.sympa"
uid, I was using the "sudo" method. Now, if wwsympa is called through
wwsympa_sudo_wrapper.pl, the received variables are as follows:

HOME --> /var/www
LOGNAME --> sympa
SUDO_GID --> 33
PATH -->
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
SUDO_USER --> www-data
SHELL --> /bin/sh
TERM --> unknown
SUDO_COMMAND --> /usr/lib/cgi-bin/sympa/wwsympa.fcgi
USER --> sympa
SUDO_UID --> 33

 I think that this is the expected behaviour. Does this mean that "sudo"
cannot be used to run wwsympa.fcgi with sympa.sympa UID and another method
must
be tried ?.

Sincerely,

Pere J Riu




Archive powered by MHonArc 2.6.19+.

Top of Page