It is throwing me an error for this image http://latimesblogs.latimes.com/.a/6a00d8341c630a53ef015390f86c4f970b-600wi.

Is this image a different type that media cant handle or is it only me who is getting the error ?

Please let me know if media module is accepting the above image.

Thanks

Comments

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)

Looks like there's multiple problems with trying to grab an URL like that.

1. The URL doesn't have an extension. I don't think this alone would cause a problem, however it could potentially cause problems.
2. The server is not returning a valid Content-Type for what type of file it is. It should be returning Content-Type: image/jpeg. You can see the headers with http://web-sniffer.net/?url=http://latimesblogs.latimes.com/.a/6a00d8341...

kiranch@vt.edu’s picture

The URL does not have an extension but it is returning the content type image/jpeg.

if you query web-sniffer.net with http://latimesblogs.latimes.com/.a/6a00d8341c630a53ef015390f86c4f970b-600wi it is giving this result http://web-sniffer.net/?url=http://latimesblogs.latimes.com/.a/6a00d8341...

you have queried it with .jpg extension to the url but there is no extension to this one

Dave Reid’s picture

Hrm, I've definitely seen it returning "text/html; charset=utf-8" that content-type header. The response seems inconsistent.

kiranch@vt.edu’s picture

You have queried it with http://latimesblogs.latimes.com/.a/6a00d8341c630a53ef015390f86c4f970b-60... (.jpg at end) but the actual url is http://latimesblogs.latimes.com/.a/6a00d8341c630a53ef015390f86c4f970b-600wi.

I think thats why the responses are inconsistent

steinmb’s picture

Category: Bug report » Support request
Issue summary: View changes

Can we close this?

JKingsnorth’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

No further response, so closing for now. Reopen if more support is required.