Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #5806 http vs https login and resulting mailman issue
    Actions
    Infos
    #5806
    Martin Hamant (martin-h)
    2014-01-11 09:51
    2013-12-26 11:15
    2280
    Details
    http vs https login and resulting mailman issue
    When login to Tuleap using http://my-tuleap.website.me directly from the homepage login (ie: not using top-right corner "login" option : https://my-tuleap.website.me/account/login.php ) then mailman URLs are not available - since the configuration file /etc/httpd/conf.d/mailman.conf is not included from /etc/httpd/conf/httpd.conf (but it is included from /etc/httpd/conf/ssl.conf).

    The only way to access mailman URLs is https://.

    Note the malfunctioning URLs are mentioned within mailman notifications emails too !

    I think a choice should be made here : either configure the system so Tuleap can only be accessed with https:// links, or review apache configuration files.
    Mailing lists
    6.8
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Waiting for information
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Martin Hamant (martin-h)2013-12-26 11:32
    Hi Yannis and thanks,

    Okay, indeed, as it forces to https, it "solves" the problem for new MLs. But anyway I have a fresh Tuleap 6.8 installation and was able to create a ML for which all 'http' links (http://http://my-tuleap.website.me/mailman/...) led to a 404.

    I now have such a ML which is somehow "broken", as it mention http:// links everywhere.

    Default installation should not permit such things, or Tuleap should be compatible with regular http links.
    User avatar
    Yannis ROSSETTO (rossettoy)2013-12-26 11:22
    Hello,

    You can actually force Tuleap using SSL. In /etc/codendi/conf/local.inc, you can modify the variable named $sys_force_ssl from 0 to 1.
    Then, restart your apache service.

    Does it resolve your issue ?
    • Status changed from New to Waiting for information
    • Assigned to changed from None to Yannis ROSSETTO (rossettoy)