HTTP Content-Type not detected.

Posted by John 2 years 13 weeks ago

John

mobiForge Newbie

Posts: 5

Joined: 5 years ago

[offline]

I think this has already been posted, but I can't quickly find that post.

WARN
MIME type was detected as application/vnd.wap.xhtml+xml;charset=UTF-8

I think Mobi.Ready throws up it's arms when it sees a charset appended to a Content-type.

AND is ECMAScript so bad?

Most modern phones circa 2007 and newer all have AJAX. Are we saying AJAX on a phone is bad?

Blackberrys, iPhones, HTC, Nokia S60, Sony Ericsson NetFront 3.4 the list goes on.

I'd say ECMAScript should just be an information 'note'.

Just a thought.

John.

Posted by ruadhan 2 years ago

ruadhan

Mobile Champion

Posts: 710

Joined: 5 years ago

[offline]

Hi John, thanks for the feedback. We'll look into this 'charset' issue - it does feel familiar like it has come up before....

Ok, after a bit of searching I see that it was mentioned in the comments on this page:
http://mobiforge.com/testing/story/fixit-mime-types

In this case it was for a different reason, but we'll check it out anyway just to be sure.

John wrote:

AND is ECMAScript so bad?

Most modern phones circa 2007 and newer all have AJAX. Are we saying AJAX on a phone is bad?

Blackberrys, iPhones, HTC, Nokia S60, Sony Ericsson NetFront 3.4 the list goes on.

I'd say ECMAScript should just be an information 'note'.

Agree with you fully that devices are getting better and better. However there are still a whole load of devices that can't handle AJAX. Regardless of this though, ready.mobi checks against the W3C mobileOK Basic tests, and in particular in this case we need to test against the guidelines here .

In the future we'd like to address this issue, so that we can differentiate usefully between devices that can or can't handle AJAX.

Ruadhan O'Donoghue
dotMobi