Resource interpreted as image but transferred with MIME type text/html.

1,247 views
Skip to first unread message

Ciul

unread,
Feb 7, 2011, 7:30:00 AM2/7/11
to Google Maps JavaScript API v3
Hi pals.

It is kinda rare problem.

In one of my maps sites I get this warning:

Resource interpreted as image but transferred with MIME type text/
html. csi:-1

There seems to be an image that is understood as a html, but don't
know why since I almost copied and pasted the code from one example to
other and this doesn't happen on the first one.

regards,
Ciul

Ciul

unread,
Feb 7, 2011, 7:40:58 AM2/7/11
to Google Maps JavaScript API v3
The resource that is causing the problem is from google maps, the
Header is this:

Request URL:http://gg.google.com/csi?
v=2&s=mapsapi3&action=apiboot&rt=jl.128,mc.308,smv.778,mb.899,vt.
1757,prt.1757,plt.1577,mt.1761&size=497x404&maptype=m
Request Method:GET
Status Code:204 No Content

The Request Headers:

Accept:*/*
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:es-ES,es;q=0.8
Cache-Control:max-age=0
Connection:keep-alive
Cookie:NID=43=MFpSNBfYxWW-
rOSERoAZ_nzow8qTw_UXgQvL00IGtqQLzgMOkuWjqGaS7N8p1sViZfJqhUv-
w96Su6_x1sP7qmgRXCofRi8SglcvmBUeR-YIVo7adSDbusz6tahG5arR;
PREF=ID=e93f401cc3ff2eac:U=0a2355c9d75345b0:FF=0:TM=1296872506:LM=1296919548:GM=1:S=-
WvDwhQYT3wFNOEQ;
SID=DQAAAL4AAAAaJiJ6Z0iKZOuMrzPDpFXag39M72OdPPDMzeJTlndX0HP8iniyTHly1j7Pi3wd9l5E0h7jrdN4GkCM3DMCDcGJr_oPXkVN-
YlKJU2u5AZmBt5cA-
y11_TZfu7tYNY12PX9eEIj0ZADEwSHM9htz5NidN8NXKJqqj3abaCi8UHrkUG_rjoN9Qa8htrihyRjgx-
jvb9aFvGqkk6G4FHSo3RpaTxEwVty2GuCUWXvQ5k3C8REdsPnblV7SH1yVa7TG3A;
HSID=AycHn4fjSfBFpj23Z; rememberme=false
Host:gg.google.com
Referer:http://localhost/ci/index.php/tour/monteria
User-Agent:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/
534.13 (KHTML, like Gecko) Chrome/9.0.597.84 Safari/534.13

Ciul

unread,
Feb 7, 2011, 7:44:55 AM2/7/11
to Google Maps JavaScript API v3
Also happening on a live site that wasn't giving any problem before.

http://labs.quillamwa.com/map/distancewidget/

Help :(

Ben Appleton

unread,
Feb 7, 2011, 5:24:49 PM2/7/11
to google-map...@googlegroups.com

This is a logging beacon. It records the time to load the javascript, tiles and so on. The server responds with HTTP 204 which, being an empty response, should not require a MIME type. Which browser is complaining?

> --
> You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
> To post to this group, send email to google-map...@googlegroups.com.
> To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
>

Ciul

unread,
Feb 7, 2011, 10:03:52 PM2/7/11
to Google Maps JavaScript API v3
Google Chrome is the browser complaining.

Firefox doesn't complain at all.

Help :(

On 7 feb, 17:24, Ben Appleton <apple...@google.com> wrote:
> This is a logging beacon. It records the time to load the javascript, tiles
> and so on. The server responds with HTTP 204 which, being an empty response,
> should not require a MIME type. Which browser is complaining?

Ben Appleton

unread,
Feb 7, 2011, 10:52:41 PM2/7/11
to google-map...@googlegroups.com
Don't panic, it's only a warning :-)

I suggest you file a bug with chromium (http://code.google.com/p/chromium/issues/entry).

- Ben

Tristan Seifert

unread,
Feb 7, 2011, 11:15:53 PM2/7/11
to google-map...@googlegroups.com
Maybe you need to explicitly send something like "Content-Type: image/png" on the server side. 

Regards,
Tristan Seifert
1 (408) 364-6384
Sent from my iPhone

Ben Appleton

unread,
Feb 7, 2011, 11:36:07 PM2/7/11
to google-map...@googlegroups.com
I don't think that makes sense for an empty response. The content of the response is not a PNG.

Ciul

unread,
Feb 8, 2011, 6:23:51 AM2/8/11
to Google Maps JavaScript API v3
The rare thing is that it wasn't happening before and it's the same
code than before.

Since Google Maps Js API has been changed/updated a lot these days,
there could be the problem.

I will post the error on that chromium link you gave me Ben (thanks
for that).

Regards,
Ciul
Reply all
Reply to author
Forward
0 new messages