Images with missing/wrong extensions #1247

NielsKSchjoedt opened this Issue Oct 16, 2013 · 3 comments

3 participants


I have been struggling a lot with issues concerning remote image paths that does not have a regular image extension, and hence cannot be processed by carrierwave. This is often the case with remote images on image servers etc. E. g. "" The file does not have a .jpeg extension, but the content_type is always correct in those examples. In this case would return "content-type"=>"image/jpeg".

The other day I stumbled upon this solution and I'm wondering why this is not the default actually?

CarrierWave member

Until yesterday this would've required adding a mime-types dependency. But now, as we already have one, I don't see any reason an approach like this shouldn't be the default.

CarrierWave member


CarrierWave member

Closing in favor of #1248

@bensie bensie closed this Feb 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment