AFAIK according to W3C spec, mime Content-Type header (type/subtype) is not case sensitive. That is, image/jpeg, Image/Jpeg and image/JPEG - all mean the same.
I agree with Robert, I guess the issue you are having is platform and implementation specific. On Wed, Apr 29, 2009 at 8:03 PM, Robert Walker < [email protected]> wrote: > > Rick Lloyd wrote: > > Simply put, I have a view/new... that accepts an image file and uses > > attachment_fu in the model to store the file and thumbnail on the > > filesystem. The view/index... puts up the thumbnails as "link_to" > > pointing at their respective full size images. I've been feeding in > > jpeg image files and using rmagick as the image processor. > > > > All works as advertised as long as the filename's type is lowercase. > > i.e.: > > file.jpg === good > > file.JPG === bad > > I'm not completely sure how different browsers treat this, but I do know > this: On many file systems (expecially UNIX based ones) "file.jpg" and > "file.JPG" are different files entirely since the file system itself is > case sensitive. > -- > Posted via http://www.ruby-forum.com/. > > > > -- Anupom http://syamantics.com ______________________________ What are you doing here?? Go Race!!! http://www.mobracer.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
