View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009333 | mantisbt | other | public | 2008-07-02 11:06 | 2019-02-06 13:04 |
Reporter | danielrigal | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Linux | OS | OpenSUSE | OS Version | 10.3 |
Product Version | 1.1.0 | ||||
Summary | 0009333: Wrong protocol when using Apache mod_proxy as a reverse proxy to access a Mantis service. | ||||
Description | We use Apache HTTP Server's mod_proxy facility on our extranet server to stitch together a range of services on internal servers and to add SSL on top. When we do this to an internal Mantis service we find that most of it is fine but a few parts are linked as "http" not "https".
Removing all use of %path% from config_inc.php fixes the first two problems by making relative paths but the confirmation link needs to be a full URL so I can't see how to fix that. | ||||
Steps To Reproduce | Set up a Mantis server running on an insecure server (http). | ||||
Tags | No tags attached. | ||||
This is a major bug IMO, I am using Mantis 1.2.12 Relationship : 0013056 |
|
Yes, there's totally a link with 0013056 I'd say the main problem is that Mantis uses absolute paths. (personal opinion: why in the world does it use absolute paths ?) |
|
Committed / pushed a change: https://github.com/mantisbt/mantisbt/pull/1459 |
|