Build: #56 failed Changes by Marc

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
12 seconds
Labels
None
Agent
Default Agent
Revision
14cc4f3ae2b6a5b1000f956599537dd88a0c937d 14cc4f3ae2b6a5b1000f956599537dd88a0c937d
Failing since
#1 (Manual run by Marc)
Fixed in
#124 (Manual run by Marc)
No failed test found. A possible compilation error occurred.

Responsible

This build has been failing since #1
No one has taken responsibility

Code commits

Author Commit Message Commit date
Marc Marc 14cc4f3ae2b6a5b1000f956599537dd88a0c937d 14cc4f3ae2b6a5b1000f956599537dd88a0c937d Merge branch '3.1.x' into 3.2.x
Marc Marc dccb5564d2ed2e3e2247bd481c4ba70a6d1317a4 m dccb5564d2ed2e3e2247bd481c4ba70a6d1317a4 Merge pull request #4438 from danchr/ticket/12133
[ticket/12133] fix download file names for WebKit-derived browsers
Dan Villiom Podlaski Christiansen <danchr@gmail.com> Dan Villiom Podlaski Christiansen <danchr@gmail.com> ce48b4de57e55ebdb6ee4bbc2eac2f81998cc671 m ce48b4de57e55ebdb6ee4bbc2eac2f81998cc671 [ticket/12133] fix download file names for WebKit-derived browsers
All browser engines that descend from WebKit declare themselves as
Safari in the user agent, including Chrome. Currently, the code
assumes that any Safari-like browser cannot handle the RFC-compliant
filename syntax. At least for recent versions of Safari, this is no
longer the case, and the legacy syntax results in URI-quoted
filenames. Using the standard syntax works as expected in both Safari
9 and Chrome 45.

The ticket reporting this issue is from January 2014, so we can safely
ignore compatibility: any browser still relying on the previous
behaviour is unlikely to receive security updates.

PHPBB3-12133

Jira issues

IssueDescriptionStatus
Unknown Issue TypePHPBB3-12133Could not obtain issue details from Jira