Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 6 antwoorden
  • 4 hebben dit probleem
  • 1 weergave
  • Laatste antwoord van 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?

Alle antwoorden (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.