We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Downloads a php page as a file instead of loading and displaying

  • 1 resposta
  • 12 têm este problema
  • 1 visualização
  • Última resposta por cor-el

more options

I reset a client's .htaccess file to process .html files through php.

As a consequence, FF downloaded instead of loading one of the html files. When I removed the .htaccess directive, this page still refused to load until I cleared my recent cache.

I found an old, locked, 2008 thread on this bug https://support.mozilla.com/tiki-view_forum_thread.php?forumId=1...

One user of this thread suggested that the problem was due to the use of UTF-8 charset. However, my page uses charset=iso-8859-1. This is a very simple XHTML 1.0 Strict page. The doctype is not the problem as it is character for character identical to other pages that do not exhibit this problem. The page validates through my web editor and at http://validator.w3.org/

The locked thread suggested editing the profile folder and removing the mimetypes.rdf file. This is NOT a solution for a public web site. There are huge numbers of casual web users who user FireFox but would not begin to have a clue about solving this problem.

Until this bug is fixed, I need some sort of work around that I can implement in my file on the server. Here's hoping that someone in the two years since the first posting has discovered one!!

I didn't include a link to the affected page because I don't yet have a test web page that exhibits the problem. It appears to be random -- I copied the page to a test web site (same server, same web hosting company), set .htaccess to process through php and the page loaded fine!!!

I reset a client's .htaccess file to process .html files through php. As a consequence, FF downloaded instead of loading one of the html files. When I removed the .htaccess directive, this page still refused to load until I cleared my recent cache. I found an old, locked, 2008 thread on this bug [https://support.mozilla.com/tiki-view_forum_thread.php?forumId=1&comments_threshold=0&comments_parentId=1452&comments_offset=0&comments_per_page=20&thread_style=commentStyle_plain] One user of this thread suggested that the problem was due to the use of UTF-8 charset. However, my page uses charset=iso-8859-1. This is a very simple XHTML 1.0 Strict page. The doctype is not the problem as it is character for character identical to other pages that do not exhibit this problem. The page validates through my web editor and at [http://validator.w3.org/] The locked thread suggested editing the profile folder and removing the ''mimetypes.rdf'' file. This is NOT a solution for a public web site. There are huge numbers of casual web users who user FireFox but would not begin to have a clue about solving this problem. Until this bug is fixed, I need some sort of work around that I can implement in my file on the server. Here's hoping that someone in the two years since the first posting has discovered one!! I didn't include a link to the affected page because I don't yet have a test web page that exhibits the problem. It appears to be random -- I copied the page to a test web site (same server, same web hosting company), set .htaccess to process through php and the page loaded fine!!!

Todas as respostas (1)

more options

You have to make sure that the server sends the processed php file as text/html

<?php header('Content-Type: text/html'); ?>