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!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

firefox displays html codes when page served from port other then tcp port 80?

  • 6 个回答
  • 4 人有此问题
  • 1 次查看
  • 最后回复者为 ideato

more options

I have a device that serves some pages. When accessed via port 80, all is good. When accessed from another port, such as 8080, the display shows only the raw html code! An Older Firefox (2.0.0.20 (Linux)) does not do this, neither does IE 8! Can the the DOCTYPE code affect this type of operation?

I have a device that serves some pages. When accessed via port 80, all is good. When accessed from another port, such as 8080, the display shows only the raw html code! An Older Firefox (2.0.0.20 (Linux)) does not do this, neither does IE 8! Can the the DOCTYPE code affect this type of operation?

所有回复 (6)

more options

See if you block firefox from the ports by your Firewall

http://kb.mozillazine.org/Firewalls


thank you

more options

Thank you for the idea, but that is not it. Turned the firewall off, still the same. Also I can view other http servers that serve pages on port 8080 and port 8000. The html is code being sent, it is just not interpreted as html. It prints the raw code in the browser window!

more options

How does the server send those pages (content-type)?

  • Tools > Page Info > General
more options

When the page is served from port 80, it shows text/thml and standards compliance mode. When served from port 8080, it shows text/plain and quirks mode? The page content is identical. Have tried removing the !DOCTYPE line. No change. Pages are very simple, straight forward html! IE8 has no problem with this, as does my old Firefox on Linux (2.0.0.20)

more options

Finally found the issue. The server was not sending the HTTP/1.1 header with a content-type parameter in it. Added this and now pages server ok from 80 and any others. Thanks for the responses.

more options

Glad you solved it, we thank you.