Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Reply
J4y
Contributor
J4y
Posts: 27
Registered: ‎01-19-2013
My Device: Z10 Dev Edition, Playbook, every BB in-between
My Carrier:

Resource interpreted as Script but transferred with MIME warning

[ Edited ]

Has anyone seen this js warning?

I'm including a <script></script> call to a js file on an external server, and this is potentially causing an issue..

 

It comes up as a warning in the chrome console:

 

 Resource interpreted as Script but transferred with MIME type text/html: "<url/js>" 

 

Using jQueryMobile BB10 theme/webworks

Please use plain text.
Administrator
astanley
Posts: 1,382
Registered: ‎07-02-2009
My Device: BlackBerry Bold 9900
My Carrier: Bell

Re: Resource interpreted as Script but transferred with MIME warning

 

When your <script> take makes  its HTTP resource request for that URL, the remote server will associate the file extension with a MIME type and generate an appropriate HTTP response based on that type.

 

What MIME type is the remote server returning for that file type?    What is the remote URL?

 

Recommend using web inspector --> Network panel to troubleshoot the specific HTTP headers, including MIME response from the server.

Follow me on Twitter: @n_adam_stanley
-------------------------------------------------------------------------------------------------------------------------
Your app doesn't work? Use BlackBerry remote web inspector to find out why.
Please use plain text.
Developer
peardox
Posts: 1,229
Registered: ‎03-20-2011
My Device: Playbook, Z10 LE, Dev Alpha B, 2x Dev Alpha C
My Carrier: 3, Orange, Vodafone

Re: Resource interpreted as Script but transferred with MIME warning

It's not something you really need to worry about. Chrome is VERY careful. It's as paranoid about web browsers as RIM BB are about mobile data.

 

There's nothing intrinsically wrong - it's just warning you there MIGHT be something iffy

 

The message you're getting comes from something known as a content header.

 

It's like a stamp and it's not the one you expected

 

This is usually harmless (can be abused though)

 

Chrome is just warning you




Click the like button if you find my posts useful!
Please use plain text.