Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I opened a image/x-png type image in new tab, but Chrome just downloaded it.
I googled it and found that Chrome doesn’t interpret image/x-png as image file.
So, I want to edit my Chrome’s MIME type mappings. Is it possible?
Too bad you have not answered my comment, so I forgot about your question and lost the bounty. I guess my answer is even a little easier to use for you because you do not need to click any context menus in order to see the PNGs directly in the browser:
Chrome extension Redirector can be configured to replace HTTP response headers. I created a rule replacing the Content-Type header for any URL ending with “.png”:
Paste this JSON code into a text editor, save as png_rule.json and then in Redirector settings go to Rules Manager, click Files to open im-/export options and import the rule version 1:
From now on all your PNG files should be fine.
Update: replaced the simple pattern match by a stricter regex match as suggested by the author or Redirector.
Update 2: There are systems like Trac which produce URLs for PNG attachments ending in “.png”, but really being HTML pages which only embed the PNG as part of the page. In this case we need to blacklist the hosts because otherwise the HTML page’s content type would be set to image/png even though it should remain text/html. Because of Redirector‘s limitation that headers can just be overwritten for matched URLs and partial replacement, e.g. only png instead of x-png, is impossible, we need to use a rather ugly approach of explicitly excluding certain hosts in the regex match. E.g.
would exclude URLs containing either host name trac.edgewall.org or freetz.org. The full JSON to be imported into Redirector is rule version 2:
Two test URLs failing (i.e. showing empty “images” instead of HTML pages) with the previous version of the rule without blacklisting and now functioning with the new rule including blacklisting are:
It is easy to add other URLs if you know a little regex or just play around.
By the way: For Trac URLs a good alternative would be to use the common part “/attachment/ticket/” for blacklisting. This way you could blacklist all Trac installations worldwide instead of a fixed hosts list. So this is rule version 3:
Update 3: Redirector is no longer available in Chrome store, but historic versions can be downloaded from the old Redirector home page.