Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing sympa.example.com/wws/wsdl to sympa.example.com/wsdl gives 404 #1270

Closed
qulien opened this issue Nov 1, 2021 · 6 comments
Closed

Comments

@qulien
Copy link

qulien commented Nov 1, 2021

I wanted to change the sympa setup so that instead of reaching the web interface at http://sympa.example.com/wws, I could reach it simply via http://sympa.example.com. I also simplified http://sympa.example.com/sympasoap to http://sympa.example.com/soap.

To do this, I changed the following lines in /etc/sympa/sympa/sympa.conf:

  • wwsympa_url http://sympa.example.com/wwswwsympa_url http://sympa.example.com/
  • soap_url http://sympa.example.com/sympasoapsoap_url http://sympa.example.com/soap

And the following lines in /etc/apache2/conf-available/sympa.conf and sympa-soap.conf respectively:

  • ScriptAlias /wws /usr/lib/cgi-bin/sympa/wwsympa-wrapper.fcgiScriptAlias / /usr/lib/cgi-bin/sympa/wwsympa-wrapper.fcgi
  • ScriptAlias /sympasoap /usr/lib/cgi-bin/sympa/sympa_soap_server-wrapper.fcgiScriptAlias /soap /usr/lib/cgi-bin/sympa/sympa_soap_server-wrapper.fcgi

Everything seems to work as expected, with one exception:

  • sympa.example.com/wsdl gives a 404 Error instead of serving the WSDL definition.

Version

  • Sympa 6.2.40

Installation method

apt install sympa

Expected behavior

  • WSDL description can be reached via http://sympa.example.com

Actual behavior

  • http://sympa.example.com yields 404 Error

Additional information

I assume I'm missing something; would appreciate any pointers in the right direction.

@ikedas
Copy link
Member

ikedas commented Nov 1, 2021

Hi @qulien ,

Did you setup Sympa SOAP service? Please see the documentation for details.

@ikedas ikedas added the question label Nov 1, 2021
@qulien
Copy link
Author

qulien commented Nov 1, 2021

@ikedas yep, SOAP is set up. API calls also work (when using the previous URL scheme, including wws). Just couldn't get it to work without the wws yet.

@racke
Copy link
Contributor

racke commented Nov 1, 2021

What about a redirect / rewrite in your Apache configuration from wws/wsdl to wsdl?

@ikedas
Copy link
Member

ikedas commented Nov 1, 2021

@qulien , please show the full configuration you made for Apache and Sympa.

[EDIT] And Please tell the versions of Sympa, Apache and the operating system.

@ikedas
Copy link
Member

ikedas commented Nov 2, 2021

And just a thought, can you access to http://sympa.example.com/lists ?

@ikedas
Copy link
Member

ikedas commented Nov 4, 2021

I decided this issue is a duplicate of #879.

mod_proxy_fcgi always determines only one path component as SCRIPT_NAME CGI variable. Thus, with @qulien 's setting, CGI variables are set as below:

  • http://sympa.example.com/:

    REQUEST_URI=/
    SCRIPT_NAME=/
    PATH_INFO=        (empty)
    
  • http://sympa.example.com/wsdl:

    REQUEST_URI=/wsdl
    SCRIPT_NAME=/wsdl
    PATH_INFO=        (empty)
    
  • http://sympa.example.com/lists/others:

    REQUEST_URI=/lists/others
    SCRIPT_NAME=/lists
    PATH_INFO=others
    

Though expected behavior is that SCRIPT_NAME will always be / and PATH_INFO will be remainder of the path.

This bug was fixed on #879 and it was included in Sympa 6.2.56.

So this issue is closed as a duplicate issue.

@ikedas ikedas closed this as completed Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants