Platonides [2011-12-10 23:56]:
01-0557-3.jpg contains "50 4B 05 06" at offset 0x4E24B and 05-0995-2.jpg at 0x309DE. Since they're just 4 bytes at an arbitrary offset amongst "random" data, it's apparently a statistical false positive.
ok, thanks for your input!
What were you changing in the db? I don't get that "magic change back" that you report. Perhaps it was metadata update was triggering it.
mysql> SELECT img_name FROM image WHERE img_media_type <> 'BITMAP'; +---------------+ | img_name | +---------------+ | 01-0557-3.jpg | | 05-0995-2.jpg | +---------------+ 2 rows in set (0.00 sec)
mysql> UPDATE image SET img_media_type = 'BITMAP', img_major_mime = 'image', img_minor_mime = 'jpeg' WHERE img_media_type <> 'BITMAP'; Query OK, 2 rows affected (0.04 sec) Rows matched: 2 Changed: 2 Warnings: 0
mysql> SELECT img_name FROM image WHERE img_media_type <> 'BITMAP'; Empty set (0.01 sec)
[...access File:01-0557-3.jpg in browser...]
mysql> SELECT img_name FROM image WHERE img_media_type <> 'BITMAP'; +---------------+ | img_name | +---------------+ | 01-0557-3.jpg | +---------------+ 1 row in set (0.00 sec)
[...access File:05-0995-2.jpg in browser...]
mysql> SELECT img_name FROM image WHERE img_media_type <> 'BITMAP'; +---------------+ | img_name | +---------------+ | 01-0557-3.jpg | | 05-0995-2.jpg | +---------------+ 2 rows in set (0.00 sec)
so that seems a bit weird to me.
Setting these values you should be safe:
well, that didn't work either :(
but what did work, though, is a plain `convert` (without actually changing anything) and uploading that instead. this way it must have gotten rid of any "garbage" there might have been. so, thanks again. for me the problem is solved :) as far as the database issue is concerned i don't know... to be honest, as long as it doesn't affect me, i don't really care. i just don't understand what it's doing there.
cheers jens