From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] bugzilla: problem with "content-disposition" for patch files
Date: Fri, 9 Apr 2010 15:29:55 +0000 (UTC) [thread overview]
Message-ID: <hpnh5j$4bm$1@dough.gmane.org> (raw)
This may seem trivial, but it's getting to be pretty annoying.
When you click on a link to a patch file in bubzilla, the
content-disposition is sent as "attachment". This disables the
ability of Firefox users to set a default action for that file type.
Can this be fixed?
A brief explanation of the problem from http://kb.mozillazine.org/File_types_and_download_actions#Unable_to_set_an_automatic_action
In some cases, you may not be able to set an automatic download
action. This can occur when a misconfigured web server assigns an
incorrect MIME type, such as "application/octet-stream" (shown
above in SeaMonkey 1.x) or if the server assigns
"Content-Disposition: attachment" to the file download (shown at
right in SeaMonkey 1.x). [6] When this happens, the option to
always perform the same action will either be "grayed-out" (as
shown here in SeaMonkey 1.x) or, in Firefox, selecting the "Do this
automatically" option will not seem to have an effect and you will
again be asked what to do when you next encounter that file type
(see below for related bug reports). There is little you can do in
these cases because the problem is at the server end.
--
Grant Edwards grant.b.edwards Yow! NANCY!! Why is
at everything RED?!
gmail.com
next reply other threads:[~2010-04-09 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 15:29 Grant Edwards [this message]
2010-04-09 22:12 ` [Buildroot] bugzilla: problem with "content-disposition" for patch files Thomas Petazzoni
2010-04-10 0:47 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hpnh5j$4bm$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox