You can see the pages when you use Firefox but get some weird characters with IE8 or androoid phones.
Here's some technical information:
CMS Version 9.3.4.1
PHP Version 5.4.4-12
MySQL Version 5.5.28-1-log (client: 5.5.28)
Server API FPM/FastCGI
IPv6 Support enabled
DTrace Support disabled
Registered PHP Streams https, ftps, compress.zlib, compress.bzip2, php, file, glob, data, http, ftp, zip, phar, ssh2.shell, ssh2.exec, ssh2.tunnel, ssh2.scp, ssh2.sftp
Does anyone have the same problem? Do you have any ideas to solve the problem?
Christophe
Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):
linux gentoo/apache2/mysql5.0/php5.2/dragonflycms 9.1.2.1
DizfunkshunalOffline
Joined: Mar 23, 2006
Posts: 2186
Location: Some where over the rainbow
The document is being served with the text/html Mime Type which is not a registered media type for the Document Type. The recommended media type for this document is: application/xhtml+xml
Using a wrong media type for a certain document type may confuse the validator and other user agents with respect to the nature of the document, and you may get some erroneous validation errors. How to fix this problem? One of the following techniques should help:
If you are serving a static file on a Web server, changing its extension should help. Use e.g .xhtml for XHTML or .mml for MathML.
You may need to reconfigure your Web server. This Setting up MIME Types tutorial has instructions for Apache, Tomcat and IIS.
If the document is generated dynamically, the scripting language should allow you to set up the mime type: this article on MIME Types and Content Negotiation has examples in PHP, Perl, and ASP.
Mismatch between Public and System identifiers in the DOCTYPE declaration
This document uses an inconsistent DOCTYPE declaration. The Public Identifier -//W3C//DTD XHTML 1.1 plus MathML 2.0//EN declares the XHTML 1.1 plus MathML 2.0 document type, but the associated System Identifier www.w3.org/TR/MathML2/...th11-f.dtd does not match this document type.
The safest way to use a correct DOCTYPE declaration is to copy and paste one from the recommended list and avoid editing that part of your markup by hand.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
Sorry greenday2k but it's not related to the issue, check df.org index.php&prevtheme=default and you will get the same warnings without encoding issues.
1. Apache 2.4
2. Varnish proxy
3. an initial Content-Encoding header set to gzip, and a second one "empty" (should be the way around)
As happened before, try to comment-in the empty Content-Encoding header found at cmsinit.inc:84.
if (ini_get('output_buffering')) {
ob_end_clean();
// header('Content-Encoding: none');
// header('Content-Encoding: '); << this is line 84
}
I suppose the proxy or apache are not maintaining the order of sent headers.
.:: I met php the 03 December 2003 :: Unforgettable day! ::.
Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):
CloudLinux / Apache 2.4 LSAPI / MySQLi 5.6 / PHP 5.6 / DCVS
christopheOffline
Joined: Mar 08, 2005
Posts: 11
Location: France, Paris
Just in case anyone is struggling with this same issue (as we were for a very long time before finding this thread) I can confirm that commenting out the line Nano refers to above does indeed solve this problem and allows gzip compression to be implemented (previously we had to turn it off by adding 'SetEnv no-gzip dont-vary' to our .htaccess file but that's no longer necessary - yippee!)
