S
Sven Steinacker
Hi,
it seems that IE 6.0 has problems to identify the MIME type "text/xml" in
the HTTP content-type, when followed by a character-set string. E.g., when
served by the Apache server, IE correctly opens MS InfoPath (or other
registered XML editors) when receiving an xml file starting with the
following (note that Apache creates the HTTP content-type from the file
content):
<?xml version="1.0" ?>
<?mso-infoPathSolution PIVersion="1.0.0.0"
href="http://myserver.com/manifest.xsf" solutionVersion="1.0.0.606"
productVersion="11.0.5531" ?>
However, IE fails to open the same file including some arbitrary encoding
type e.g.:
<?xml version="1.0" encoding="UTF-8" ?>
<?mso-infoPathSolution PIVersion="1.0.0.0"
href="http://myserver.com/manifest.xsf" solutionVersion="1.0.0.606"
productVersion="11.0.5531" ?>
It seems there is some kind of if(content-type = "text/xml") in the IE code
instead of if(content-type.getMIME = "text/xml"). Just a guess.
Has anyone seen a good workaround for this problem for Apache and/or the
Tomact server? Is there a newer version of IE available, which fixes this
problem?
Hints very appreciated!
Sven Steinacker
Ericsson Germany
it seems that IE 6.0 has problems to identify the MIME type "text/xml" in
the HTTP content-type, when followed by a character-set string. E.g., when
served by the Apache server, IE correctly opens MS InfoPath (or other
registered XML editors) when receiving an xml file starting with the
following (note that Apache creates the HTTP content-type from the file
content):
<?xml version="1.0" ?>
<?mso-infoPathSolution PIVersion="1.0.0.0"
href="http://myserver.com/manifest.xsf" solutionVersion="1.0.0.606"
productVersion="11.0.5531" ?>
However, IE fails to open the same file including some arbitrary encoding
type e.g.:
<?xml version="1.0" encoding="UTF-8" ?>
<?mso-infoPathSolution PIVersion="1.0.0.0"
href="http://myserver.com/manifest.xsf" solutionVersion="1.0.0.606"
productVersion="11.0.5531" ?>
It seems there is some kind of if(content-type = "text/xml") in the IE code
instead of if(content-type.getMIME = "text/xml"). Just a guess.
Has anyone seen a good workaround for this problem for Apache and/or the
Tomact server? Is there a newer version of IE available, which fixes this
problem?
Hints very appreciated!
Sven Steinacker
Ericsson Germany