JSP generated content, sent as 'Content-type: text/plain' is not interpreted as HTML

VERIFIED INVALID

Status

()

Core
HTML: Parser
P3
normal
VERIFIED INVALID
18 years ago
18 years ago

People

(Reporter: Matthias Kerkhoff, Assigned: rickg)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (WinNT; U)
BuildID:    2000070408

JSP generated content, sent as 'Content-type: text/plain' is not parsed. 

Reproducible: Always
Steps to Reproduce:
1. Load a jsp-page from a server, which does not deliver the correct content 
type. (see URL for an example)


Actual Results:  The content is displayed unparsed.

Expected Results:  Not sure. I would like the same behaviour as IE, which should 
result in rendering the page. 
I assume, that the current behaviour is correct, but it prevents using JSPs on 
(some) (misconfigured) servers, over which the web-designer has no control.

This is the opposite of bug #43499. 
M16 renders the page.
Maybe, the parser could examine the DTD (which is present in the example pages) 
and decide to render or not to render depending on 
the DTD's value.
This is INVALID. If the server is misconfigured, then fix the server.

If a correctly configured server sent a file as text/plain, and it looked like
HTML to us so we treated it as text/html instead of text/plain, we would be
doing the wrong thing.

How are we supposed to know when the server means text/html and when it means
text/plain? We can't exactly write a telepathy module into Mozila...

If the server lies to us, then that's the server's fault. Fix the server. It's
not exactly difficult.

And if the web developer has no control over a server that is so fundamentally
flawed as to send out the wrong Content-Type for HTML, I would strongly 
recommend that they change providers/jobs.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID

Comment 2

18 years ago
Server problem not ours. Marking as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.