content-disposition is ignored

Bug #648471 reported by Matt Read
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Midori Web Browser
Confirmed
Medium
Unassigned
Steadyflow
Triaged
Low
Unassigned

Bug Description

Some download servers serve there files using content-disposition header. For example:

Content-Disposition: attachment; filename="diff.tar.gz"

However steadyflow has no option to support this and instead tries to determine a filename from the URI.

So, for example, downloading a file served as an attachment content-disposition from http://example.com/get_file/23rt674948 would result in a filename of 23rt674948. Which in turn means I have to go back to the webpage and determine if it was a zip, tar.gz, tar.bz2, etc. (cause in CLI it's hard to find that out ;) )

There should be an option for "determine file name automatically", so it can use the content-disposition header properly.

Tags: http
Revision history for this message
Matt Read (mattread) wrote :

OR, as another thought, it should provide a way via DBus to pass in the url AND filename of the file.

Maia Everett (linneris)
Changed in steadyflow:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Cris Dywan (kalikiana) wrote :

It should accept HTTP headers via DBus, which would also allow parsing of authentication and cookies. Otherwise all applications have to handle these details before calling the SteadyFlow API.

Changed in midori:
status: New → Confirmed
importance: Undecided → Medium
tags: added: http
Revision history for this message
Maia Everett (linneris) wrote :

I've attached a blueprint with the proposed API for passing HTTP headers. Could you comment?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.