Bug 1673270 - Bugzilla tries to open attached text files in external applications
Summary: Bugzilla tries to open attached text files in external applications
Keywords:
Status: CLOSED DUPLICATE of bug 1658655
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-07 07:55 UTC by Zdenek Dohnal
Modified: 2019-03-14 03:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 03:47:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Zdenek Dohnal 2019-02-07 07:55:12 UTC
Hi!

Old bugzilla had a feature of opening text files as other browser tab, which was convenient in way I had all relevant attachments and bugzilla report in one application (even better experience is when user has tree style tab firefox plugin - all relevant attachments are opened under parent tab - bugzilla report).

Bugzilla 5 now tries to open text files in external app, which makes it harder to cope with - if I don't mention usage of more resources to run other app, then other cons is it is unpleasant to open external text editor every time I want to see the text file (imagine you needed hard reset of PC, you log in, open browser and now instead of just seeing already opened tab with contents of text file, you again need to open that external app...)

Would you mind implementing the feature of old bugzilla?

Comment 1 Petr Menšík 2019-02-19 15:48:19 UTC
I am afraid it seems to be intentional.

wget -S -O /dev/null "https://bugzilla.redhat.com/attachment.cgi?id=1521102"
--2019-02-19 16:41:58--  https://bugzilla.redhat.com/attachment.cgi?id=1521102
Resolving bugzilla.redhat.com (bugzilla.redhat.com)... 10.4.205.4
Connecting to bugzilla.redhat.com (bugzilla.redhat.com)|10.4.205.4|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  Date: Tue, 19 Feb 2019 15:41:59 GMT
  Server: Apache
  Content-disposition: attachment; filename="rndc_managed-keys_status.txt"
  X-content-type-options: nosniff
  X-frame-options: SAMEORIGIN
  X-xss-protection: 1; mode=block
  Content-length: 382
  Content-Type: text/plain; name="rndc_managed-keys_status.txt"; charset=
  Set-Cookie: Bugzilla_login_request_cookie=nKlwPdlUVB; domain=bugzilla.redhat.com; path=/; HttpOnly; SameSite=Lax
  Connection: close
Length: 382 [text/plain]

Note Content-disposition header has value attachment, introduced by RFC 1806. That instructs browser to save it by external file. It is text/plain, but is not handled by browser itself. Would it be possible to customize it to type inline, which would allow browser to open it?

1. https://www.ietf.org/rfc/rfc1806.txt

Comment 2 Jaroslav Škarvada 2019-03-13 13:50:02 UTC
In-browser view is really more comfortable (at least for me) and more efficient especially when dealing with multiple bugs/attachments. Is there any reason / use case to open it primarily through external application? If yes, could you please add configuration option for people to be able to customize it?

Comment 3 Jeff Fearn 🐞 2019-03-14 03:47:46 UTC

*** This bug has been marked as a duplicate of bug 1658655 ***


Note You need to log in before you can comment on or make changes to this bug.