Closed Bug 17412 Opened 25 years ago Closed 24 years ago

XML with CSS1 fails over server, but works when browsed locally.

Categories

(Core :: XML, defect, P3)

Product:
Core
Component:
XML
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: Ken.Sall, Assigned: jud)

References

(
URL
)

Details

(Keywords: verifyme) 

The XML file
http://www.cen.com/ng-html/xml/display/examples/collection1-css-style.xml
references a CSS1 stylesheet, collection.css, in the same directory. The
PI is simply path href="collection.css". The result is that the raw XML is
displayed; the style is ignored. However, the same files without change
when browsed locally with Milestone 10 work just fine. Note that IE5 is
able to use the stylesheet and above URL over the server with no problem.
Is there some server MIME type change that's needed perhaps? Yet why does IE5
work?

Please reply to Ken.Sall@AppNet.com. Thanks!
Status: NEW → ASSIGNED
Setting milestone to M13 for now...
Target Milestone: M13
Moving non beta-stoppers to M16...
Moving bugs out by one milestone...
Target Milestone: M16 → M17
There is a bug in the DTD selection logic in the parser.  An HTML DTD gets 
created for the above page when you load it from the server instead of an XML 
DTD.  Re-assigning to Harish.
Assignee: nisheeth → harishd
Status: ASSIGNED → NEW
Target Milestone: M17 → ---
I agree that the DTD selection logic should be smart enough to select the 
appropriate DTD. But, the core of the problem ( parser being provided with a 
wrong mime type)could be at a much higher level ( webshell/docshell ? ).

CCing rick, nisheeth, travis, and judson for input.
Moving bug to valeski's plate.  Jud, you should probably use the detection login 
in the parser to determine the proper mime type.  Selecting a mime type based on 
file extension is just not enough.
Assignee: harishd → valeski
*** Bug 34882 has been marked as a duplicate of this bug. ***
the mime type that the server sends back is the one we use, and clearly it's
sending back the wrong one in this case. servers have last say in our model, we
don't byte scan every doc that comes in.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Adding 'verifyme' keyword
Keywords: verifyme
QA Contact: chrisd → petersen
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.