I've discovered a bug in the multipart parser in Merb core 1.0.9
having to do with the binary data that an uploaded file ends with.
It's very easy to reproduce... just use the index.html I just uploaded
to the Google Groups "Files" section to upload the 1024 byte
"FailingFile" that's also there.
I expect to get a "field_is_skipped: GONE" parameter, but
params.to_yaml yields the following:
--- !map:Mash
format:
action: index
id:
file_data: !map:Mash
content_type: video/x-ms-wm
size: 1148
tempfile: !ruby/object:File {}
filename: FailingFile
controller: upload
field_is_found: PRESENT
Note the 1148 size from a 1024 file.
Any ideas what is in that file to confuse Merb?
matt
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
