Image upload failed because the extension of this file did not match the content.

[naszeaudio]

Simple photo from Samsung edge s6. Windows paint can open it, but vbulletin forum will always say 'Image upload failed because the extension of this file did not match the content.'

Extension is jpg, but filetype jpeg. Sure, but hey that not rocket science for software to try Jpeg when extension is jpg, right? How to force vbulletin to do it?

[Wayne Luke]

There is no way around this. It is triggering a security feature. Some browsers will interpret the contents of the file as they are, not as they should be. People can place javascript and other code within image files.

What you're encountering sounds like a bug and a JPEG image with a JPG extension should be recognized. I suggest opening a JIRA for this issue. You can do so here:

http://tracker.vbulletin.com/secure/CreateIssue.jspa?pid=10091&issuetype=1

[naszeaudio]

Wayne, done. Thanks

I am surprised no one picked this one up. Showstopper. Makes my users think 'a jpg problem? if this do not work, what kind of forum is that?'

[Mark.B]

I disagree that it's a showstopper, but it should be looked at.

[Jin-Soo Jo]

naszeaudio If at all possible, could you upload the image file that's having the issue to that JIRA?

Edit: Here's the JIRA link for reference: http://tracker.vbulletin.com/browse/VBV-16320

[Jin-Soo Jo]

Also is the forum in question using GD or ImageMagick? You can check by going to admincp > Settings > Options > "Image Setings" > "Image Processing Library"

[zuendy]

I think I have a similar problem.

http://www.vbulletin.com/forum/forum/vbulletin-5-connect/vbulletin-5-connect-questions-problems-troubleshooting/vbulletin-5-support-issues-questions/4350646-invalid-file-data-p1250751-jpg

[Jeanius!]

I have the same problem too.

[Jin-Soo Jo]

zuendy Thanks for the file in the other thread. I'll take a look at what's going on with it as soon as possible next week.

[naszeaudio]

Sorry guys for delay. We are using GD at the moment (as apple product users says it works better for them than imagemagick).

I understand u have sample file already.

[Kevin Sours]

We're still looking into this. My apologies for the delay. The core issue is that the file in question is tripping some security checks we have in place. The root issue is that it's relatively easy to create a completely valid image that will execute PHP code if you can convince the system to treat it as a PHP file. Unfortunately the image standards have a lot of essentially undefined sections that various cameras do some strange things with, so sorting out what a valid image looks like isn't as easy as it should be. So we need to tweak the checks to accept a wider variety of (legitimate) images, but I hope you understand why we're moving carefully on this. We think we've worked out a process that will greatly improve things.

We do have a sample image, but we could use a few more to make sure that there isn't anything out there we haven't accounted for (there probably is -- I expect this to be a iterative process)
Kevin

[amart79196]

Just to report, this problem is also in the latest version, 5.2.4 as well.

1. Is there any viable workaround to get an image posted?
2. Can we expect this to be fixed in the next release?

[Trevor Hannant]

Just to report, this problem is also in the latest version, 5.2.4 as well.

1. Is there any viable workaround to get an image posted?
2. Can we expect this to be fixed in the next release?

1. Not at this time
2. Depends on whether people provide images that have been causing issues so that they can look into these and work to resolve the issue. The more sample images that have been causing issues, the more likely the developers will be able to resolve this!

Please attach any images that are flagging up the same message to the Bug Report, NOT here:

http://tracker.vbulletin.com/browse/VBV-16320

[amart79196]

I just uploaded this file to the bug tracker.

[Wayne Luke]

We're applying a fix for this in 5.2.5. Basically, if all the other security checks pass, the image will have its metadata stripped be rewritten as a valid JPEG file. This should help workaround phones and cameras that can't follow standards.