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
Comment #1
dave reidLooks 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...Comment #2
kiranch@vt.edu commentedThe 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
Comment #3
dave reidHrm, I've definitely seen it returning "text/html; charset=utf-8" that content-type header. The response seems inconsistent.
Comment #4
kiranch@vt.edu commentedYou 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
Comment #5
steinmb commentedCan we close this?
Comment #6
jkingsnorth commentedNo further response, so closing for now. Reopen if more support is required.