-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Currently, in the fileDownloadOperation in file-operations-plugin, the targetFileName is required.
Instead, if the targetFileName is empty, the targetFileName should default to the filename parameter of the Content-Disposition header, or if not present, the filename following the last / in the URL.
I can provide a pull request if that helps. Also, the 'file-operations-plugin' JIRA component is missing, so I chose 'plugin-proposals' as the component. Can someone with permissions create the 'file-operations-plugin' component and edit this issue please?
[JENKINS-41181] preserve original filename in fileDownloadOperation
Component/s | New: plugin-proposals [ 15491 ] | |
Component/s | Original: core [ 21134 ] | |
Key | Original: INFRA-1042 | New: JENKINS-41181 |
Workflow | Original: classic default workflow [ 215156 ] | New: JNJira + In-Review [ 215157 ] |
Project | Original: Infrastructure [ 10301 ] | New: Jenkins [ 10172 ] |
Description |
Original:
Currently, in the {{fileDownloadOperation}} in file-operations-plugin, the {{targetFileName}} is required. Instead, if the {{targetFileName}} is empty, the {{targetFileName}} should default to the {{filename}} parameter of the {{Content-Disposition}} header, or if not present, the filename following the last {{/}} in the URL. I can provide a pull request if that helps. Also, the 'file-operations-plugin' JIRA component is missing, so I chose 'core' as the component. |
New:
Currently, in the {{fileDownloadOperation}} in file-operations-plugin, the {{targetFileName}} is required. Instead, if the {{targetFileName}} is empty, the {{targetFileName}} should default to the {{filename}} parameter of the {{Content-Disposition}} header, or if not present, the filename following the last {{/}} in the URL. I can provide a pull request if that helps. Also, the 'file-operations-plugin' JIRA component is missing, so I chose 'plugin-proposals' as the component. |
Description |
Original:
Currently, in the {{fileDownloadOperation}} in file-operations-plugin, the {{targetFileName}} is required. Instead, if the {{targetFileName}} is empty, the {{targetFileName}} should default to the {{filename}} parameter of the {{Content-Disposition}} header, or if not present, the filename following the last {{/}} in the URL. I can provide a pull request if that helps. Also, the 'file-operations-plugin' JIRA component is missing, so I chose 'plugin-proposals' as the component. |
New:
Currently, in the {{fileDownloadOperation}} in file-operations-plugin, the {{targetFileName}} is required. Instead, if the {{targetFileName}} is empty, the {{targetFileName}} should default to the {{filename}} parameter of the {{Content-Disposition}} header, or if not present, the filename following the last {{/}} in the URL. I can provide a pull request if that helps. Also, the 'file-operations-plugin' JIRA component is missing, so I chose 'plugin-proposals' as the component. Can someone with permissions create the 'file-operations-plugin' component and edit this issue please? |
Component/s | New: file-operations-plugin [ 22428 ] | |
Component/s | Original: plugin-proposals [ 15491 ] |
Assignee | Original: R. Tyler Croy [ rtyler ] | New: Suresh Kumar [ pskumar448 ] |