From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] bugzilla: problem with "content-disposition" for patch files
Date: Sat, 10 Apr 2010 00:47:15 +0000 (UTC) [thread overview]
Message-ID: <hpohqj$lae$1@dough.gmane.org> (raw)
In-Reply-To: 20100410001231.01b7d6f5@surf
On 2010-04-09, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> On Fri, 9 Apr 2010 15:29:55 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> 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?
>
> I agree, this would be nice.
I had hoped there might be a way to fix it in Firefox, but the Firefox
dev's really have a stick up their rear on this one. They're
absolutely positive they're right and everybody else in the world is
wrong. People have been asking for this to be fixed in Firefox for
years and years (other browsers don't seem to have this "feature"),
but the Firefox devs are sticking to the "one true path" with a
religious fervor. From the looks of their bug-tracking system, they
must have one dev who's full time job is to change the state of new
reports of this problem to "duplicate" and tell all of the posters of
"me too, please fix this" comments to frack off.
They claim letting users set a default handler for files that are
"content-disposition: attachment" would be "security problem" --
though I've read and was completely unable to follow their reasoning.
If only they put as much effort into plugging other security holes as
they put into defending this feature.
I think it's a case of "security problem" being double-speak for "the
bug doesn't bother us, so we're not going to fix it."
So, the only hope is that bugzilla could be changed. [I don't really
understand the reasoning behind bugzilla's setting the
content-disposition to "attachment" either, but I haven't looked into
that side of it.]
--
Grant
prev parent reply other threads:[~2010-04-10 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 15:29 [Buildroot] bugzilla: problem with "content-disposition" for patch files Grant Edwards
2010-04-09 22:12 ` Thomas Petazzoni
2010-04-10 0:47 ` Grant Edwards [this message]
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='hpohqj$lae$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