ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001285 | ClearOS | app-flexshare - Flexshares | public | 2013-08-19 15:10 | 2019-09-24 03:23 |
| Reporter | user2 | ||||
| Assigned To | |||||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | suspended | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0001285: Improve HTTPS usability in web server access to Flexshares | ||||
| Description | HTTPS handling in Flexshare (and in general!) is non-intuitive at times. - Only one SSL certificate is permitted per IP, so hostname-based SSL is a bit misleading. Though https://flex1.example.com [^] and https://flex2.example.com [^] can co-exist, only one SSL certificate is permitted. - If a user disables SSL support, the hostname-based Flexshare (e.g. flex1.example.com) is removed. However, if other SSL Flexshares are enabled, the disabled https://flex1.example.com [^] Flexshare will still resolve, but it will point to a different Flexshare. Confusing, but that's an HTTPS-ism that's hard to get around. Note: the path-based Flexshare (e.g. example.com/flexshare/flex1) remains, but it should be possible to remove the HTTPS path-based access. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-08-19 15:10 | user2 | New Issue | |||
| 2013-08-19 15:11 | user2 | Status | new => confirmed | ||
| 2013-08-20 11:19 | user2 | Checkin | |||
| 2013-08-20 11:19 | user2 | Note Added: 0000980 | |||
| 2019-09-24 03:23 | NickH | Note Added: 0012381 | |||
| 2019-09-24 03:23 | NickH | Status | confirmed => closed | ||
| 2019-09-24 03:23 | NickH | Resolution | open => suspended | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||