FS#15865 - {bugtracker} attached files should have a MIME type attached/sent
Attached to Project:
Arch Linux
Opened by majiq (majiq) - Saturday, 08 August 2009, 23:47 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 March 2017, 14:17 GMT
Opened by majiq (majiq) - Saturday, 08 August 2009, 23:47 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 March 2017, 14:17 GMT
|
Details
Description:
Upon uploading a patch for an xml file, it seemed upon viewing it that the uploaded file had no content besides the header. Eventually the fact that the xml tags became interpreted was evident. I don't know how difficult it is, but simply sending a MIME of text/plain before the file should make all xml items display properly. As long as only text is uploaded to the bugtracker, which I know it's not (screenshots). Possibly an extension sensitive function which defaults to text. I think this is fairly important because some people just copy the patch info into a file or click on it from the bugtracker to read what is being changed, and then miss the items interpreted by the browser. In a large patch that affects multiple files, some people might not notice the fact that some xml information is missing. Lastly, it will fix future problems like on the task listed below, where the same file is uploaded multiple times. Steps to reproduce: Visit http://bugs.archlinux.org/task/15633 , and look at the supplied patch in the web browser. Then look at the source of the page and note the difference. |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 15 March 2017, 14:17 GMT
Reason for closing: Deferred
Additional comments about closing: Attachments are set to download by default now, so this is not an issue anymore.
Wednesday, 15 March 2017, 14:17 GMT
Reason for closing: Deferred
Additional comments about closing: Attachments are set to download by default now, so this is not an issue anymore.
It sounds like we'd have to hack flyspray for this, right? Should we try that, or file a similar request upstream?
Or is it something we can fix through server configuration or some other way?
It seems like a configuration option.
if server access/administration isn't too troublesome.
This could be incorrectly assigned, but things change over three years. I assume it still could be a simple configuration option?