Description of problem:
The console.log file sometimes may contain non printable characters such as color codes for example. The result is that the file is treated as binary and the user can't read it directly in the browser but instead is offered to download the file. This is also problematic because by default (at least for me) GNOME tries to open the file with gedit which fails because it can't determine text encoding.
This RFE is to make it possible that the console.log is viable in the browser directly. It's 99% text so forcing text/plain sounds safe.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try downloading a console.log from a Beaker job. For example from here https://beaker.engineering.redhat.com/jobs/3405
*** This bug has been marked as a duplicate of bug 600098 ***