169523 2008-08-21 10:03:51 +0000 site displays completely wrong (konq3, firefox, etc work fine) 2008-08-22 16:49:22 +0000 1 1 2 Applications konqueror general unspecified Gentoo Packages Linux RESOLVED FIXED NOR normal --- 0 dizzy konqueror-bugs-null andresbajotierra maksim 0 oldest_to_newest 639656 0 dizzy 2008-08-21 10:03:51 +0000 Version: 4.1.00 (using KDE 4.1.0) Compiler: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1) OS: Linux Installed from: Gentoo Packages Hello I have just noticed that a site I often use "www.monosit.ro" has changed the design and does not display correctly on konqueror4. If I try to display it with firefox3 or konqueror3 it looks fine. I asked some people on freenode/#kde to confirm this and they also confirmed the same behavior. Please help, thanks! 639717 1 andresbajotierra 2008-08-21 14:06:35 +0000 Using KDE 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) (KDEmod) in ArchLinux i686: I can confirm this. Seems like the CSS isn't loaded. 639748 2 maksim 2008-08-21 16:59:12 +0000 For some reason we get mimetype as ":", which isn't a valid stylesheet mimetype and hence gets it ignored in strict mode. The server doesn't send anything (bad server!) 639750 3 maksim 2008-08-21 17:00:54 +0000 Oh, actually is does: Content-Type: : so KIO is right here. Now I need to figure out whether other browsers are parsing this differently (hmm, may be via XHR?), or if something can override the mimetype check... 639772 4 maksim 2008-08-21 18:49:07 +0000 http://lists.kde.org/?l=kde-commits&m=121933684323332&w=2 639882 5 dizzy 2008-08-22 09:03:21 +0000 Thanks for the workaround. So you are saying that tho the css files are php documents (so their contents is probably dynamically generated) they should still come with Content-Type: text/css right? I suppose they need to use header() PHP function or something similar :) 639976 6 maksim 2008-08-22 16:49:22 +0000 You're welcome. And yes, stylesheets served to web pages in strict mode have to have the mimetype text/css, or no mimetype at all. Thing is, the server actually sends a malformed content-type header altogether. That it's PHP on the server end doesn't matter, since content-type describes the type of the data we get / how we should handle it --- it makes no difference to the displaying application if it was hand-coded or generated by PHP or Perl or Rails, or ASP or whatever.