https://bugzilla.wikimedia.org/show_bug.cgi?id=25163
--- Comment #11 from Bawolff (Brian Wolff) <[email protected]> --- (In reply to Jackmcbarn from comment #10) > A few questions: Is IE's autodetection really so bad that we need to reject > valid binary images because they have something that looks like HTML in > them? Also, how did HTML (or something that looks sort of like HTML) end up > in an EXIF tag in the first place? If there's no non-contrived way, then is > this worth worrying about? Finally, is the right way to "fix" this really to > link users to a page telling them how to remove EXIF data? IE6 has shockingly bad content detection Html ends up in exif tags mostly from people adding things like <a href=... to exif tags One possible alternative fix (would need review safety of this) i think would be to have mw modify the file to add 255 bytes of padding (jpg allows padding markers in file immediately after the first marker. The other case this issue happens is certain xml formats, which allow whitespace padding). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
