Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Firefox ignores response header Content-Type

  • 2 réponses
  • 1 a ce problème
  • 11 vues
  • Dernière réponse par benszone

more options

I have a configured nginx server returning the following headers when serving plain, non-UTF encoded text files.

Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline

When the text files contain ANSI escape sequences (Standard ECMA-48) Firefox will often ignore the server Content headers to use a guess determined by the file extension. But the guess is often wrong and forces the browser to download the file instead of displaying it in the tab.

Cause: document Type: application/x-vnd.mozilla.guess-from-ext; charset=ISO-8859-1

Is this intended behavior and is there anything else I can do to encourage Firefox to display the text file in a browser tab? As this is not the same behavior with other browser engines such as Blink or Trident.

6 sample files, all refuse to display in Firefox except 'r5-WTF4.ans' https://retrotxt.com/e/

I have a configured nginx server returning the following headers when serving plain, non-UTF encoded text files. Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline When the text files contain ANSI escape sequences (Standard ECMA-48) Firefox will often ignore the server Content headers to use a guess determined by the file extension. But the guess is often wrong and forces the browser to download the file instead of displaying it in the tab. Cause: document Type: application/x-vnd.mozilla.guess-from-ext; charset=ISO-8859-1 Is this intended behavior and is there anything else I can do to encourage Firefox to display the text file in a browser tab? As this is not the same behavior with other browser engines such as Blink or Trident. 6 sample files, all refuse to display in Firefox except 'r5-WTF4.ans' https://retrotxt.com/e/
Captures d’écran jointes

Modifié le par benszone

Toutes les réponses (2)

more options
more options

cor-el said

See:

Hi thanks, but it seems with Firefox nosniff only works with script or css, but not text/plain.

Note: nosniff only applies to "script" and "style" types.

nosniff

   Blocks a request if the requested type is
       "style" and the MIME type is not "text/css", or
       "script" and the MIME type is not a JavaScript MIME type.