View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023409 | mantisbt | html | public | 2017-09-28 07:24 | 2018-04-12 07:55 |
Reporter | tseel | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 2.6.0 | ||||
Summary | 0023409: Use RFC2231 file name encoding for all browsers | ||||
Description | Currently Chrome and IE are handled specially when the content disposition header for a file download is created. This handling has at least for filenames which include brackets and other special characters the effect, that these chracters are html encoded and not transferred to the browser this way. The behavior is the same for IE11 and Chrome 61, as they are handled with a workaround implemented in 2009 (see 0011075). FF 55 receives the correct names as it receives a standard content disposition header. It seems that this workaround is no longer needed and can be removed. A short test which removes the workaround of https://github.com/mantisbt/mantisbt/commit/f2035d37ccd7b623a9cdef895a8cc1b0e1779e27 in core/http_api.php show the expected behavior. | ||||
Steps To Reproduce |
| ||||
Tags | No tags attached. | ||||