This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Hello mobileOK checker team, although - relating a linked jpg - Firebug says "image/jpeg; charset=utf-8", the checker says "check that the format of the resource(s) below is correctly set in the HTTP Content-Type header" (link_target_format error)!? The format is set everywhere including subfolders (by .htaccess) and Firebug says that each, but when a file is in a link there's a problem!? Adding type="" and charset="" into the link doesn't help! Seems to be a bug. Please take care of it. Regards, Holger
Hi Holger, Thanks for the report. Could you share the address of a page that exhibits the issue? A quick check on a page that links to a JPEG image does not reveal the bug, so I suspect there's something more going on here. Note the mobileOK checker uses a specific set of HTTP headers to emulate a "mobile" browser when it sends the requests and the content-type it receives in the HTTP response may not be the same as the one advertised by Firebug which uses the usual Firefox request headers.
> Could you share the address of a page that exhibits the issue? Here it is: http://holgerduew.atwebpages.com/example.php (same thing with the txt file) Besides, now the jpg file isn't found although it's shown on the page!?!? Please examine it with a fine-tooth comb. PS: CSS 1 is totally outdated (no mobile phone of today has only CSS 1, even an ancient one via firmware update) and CSS 2.1 is Beta, so please accept (additionally) latest Recommendation (!) CSS 2.0 which every mobile phone of today has!
(In reply to comment #2) > > Could you share the address of a page that exhibits the issue? > Here it is: http://holgerduew.atwebpages.com/example.php (same thing with the > txt file) > Besides, now the jpg file isn't found although it's shown on the page!?!? > Please examine it with a fine-tooth comb. Thanks for sharing the link. The server returns an "Internal Server Error" when the mobileOK Checker requests the image. Since the image is rendered on traditional browsers, it means that there is something in the HTTP request sent by the mobileOK Checker that the server does not like. I had a look and it seems the internal server error (HTTP status code 500) is returned because the request does not contain a "Referer" HTTP header field. Most browsers include a "Referer" HTTP header field. Note it is an optional HTTP header and should not be used to filter responses. Users and browsers may choose not to send a Referer HTTP header for privacy reasons for instance, see: http://tools.ietf.org/html/rfc2616#section-15.1.2 You can reproduce the error using e.g. Firefox and the Modify Headers extension to filter the Referer HTTP header. I'll try to clarify the error message returned by the Checker to point out that the error received by the mobileOK Checker may be a consequence of the particular HTTP headers it uses to retrieve resources. > PS: CSS 1 is totally outdated (no mobile phone of today has only CSS 1, even an > ancient one via firmware update) and CSS 2.1 is Beta, so please accept > (additionally) latest Recommendation (!) CSS 2.0 which every mobile phone of > today has! In terms of functionalities, CSS 1 is close to CSS Mobile Profile 2.0: http://www.w3.org/TR/css-mobile/ CSS Mobile Profile 2.0 would be more appropriate but it is not a Web standard yet (it is a "Candidate Recommendation" at this stage) and we had to fallback to CSS Level 1, completed with one or two features specified in the mobileOK Basic Tests 1.0 standard: http://www.w3.org/TR/mobileOK-basic10-tests/#validity