Bug 442 - Does not correct link to the attached document
: Does not correct link to the attached document
Product: Websites
Classification: ROSA Infrastructure
Component: Bugzilla
: unspecified
: All Linux
: Normal normal
: ---
Assigned To: Pavel Shved
: ROSA Linux Bugs
Depends on:
  Show dependency treegraph
Reported: 2012-06-25 18:02 MSD by Postnikov Dmitry
Modified: 2012-06-25 19:03 MSD (History)
0 users

See Also:
RPM Package:
Bad POT generating:

example of correct behavior (73.76 KB, image/png)
2012-06-25 18:06 MSD, Pavel Shved
GCU1 (247.74 KB, image/png)
2012-06-25 18:11 MSD, Postnikov Dmitry
FFU1 (200.16 KB, image/png)
2012-06-25 18:11 MSD, Postnikov Dmitry

Note You need to log in before you can comment on or make changes to this bug.
Description Postnikov Dmitry 2012-06-25 18:02:33 MSD
Does not correct link to the attached document. Link to PNG file is http://bugs.rosalinux.ru/attachment.cgi?id=308 When you click on the link requests save attachment.cgi
Similarly, in letters from Bagzilla.
Expample bug 441.
Comment 1 Pavel Shved 2012-06-25 18:06:16 MSD
Created attachment 309 [details]
example of correct behavior

What is your browser?  Could you try Firefox, please (it works for me in it?)
Comment 2 Postnikov Dmitry 2012-06-25 18:10:58 MSD
Google Chrome Ubuntu 10.04 - not work.
Firefox Ubuntu 10.04 - work.
See att.
Comment 3 Postnikov Dmitry 2012-06-25 18:11:18 MSD
Created attachment 310 [details]
Comment 4 Postnikov Dmitry 2012-06-25 18:11:33 MSD
Created attachment 311 [details]
Comment 5 Pavel Shved 2012-06-25 19:03:08 MSD
Your Chromium browser is probably too old.  I installed Chromium, and I can't find any settings in this browser (as of Chromium version 13.0.782.215) that could fix this.  However, Anton has Chromium 19.*, and in his browser attachments are named correctly.

My current understanding is like this.  The file name comes from HTTP headers (Content-disposition) sent alongside the file itself.  Browsers should account for them, but older versions of Chromium apparently do not.  You should probably upgrade your browser.

I can't say that the bug is unfixable, I could fix it at bugzilla side, but I don't think it's a really good investment or resources, sorry :(

Reopen if upgrading Chromium doesn't work, please.