Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

26
  • 2
    Related: meta.stackexchange.com/q/261925/245360 Commented Aug 3, 2015 at 9:13
  • Looks like it was created by some fancy software, in the raw response I see "Adobe Photoshop CS3 Windows", and this format is simply not supported by imgur, which tries to analyze the picture. Commented Aug 3, 2015 at 9:23
  • It still seems a regular JPG to me. @ShadowWizard Commented Aug 3, 2015 at 9:24
  • 2
    That error happens inside imgur; as such, I can't tell you what specifically it doesn't like (the error message is fairly generic) - as @ShadowWizard notes: presumably there is an encoding option in use that imgur doesn't like. Options: 1) imgur change their API to allow the format; 2) you re-save the file to tweak the encoding; 2 seems like a more timely fix Commented Aug 3, 2015 at 14:39
  • Agree with @Marc that this probably isn't worth spending much time on, unless we'll see this happening more. Commented Aug 3, 2015 at 14:50
  • @MarcGravell "the issue seems to be on the SE's imgur interface where some kinda URL validation (and/or filename check) is happening before the image upload" - quoted HackerKarma below Commented Aug 3, 2015 at 15:05
  • @Ooker SE's imgur interface from where the API sends the data to imgur... I would like to see what the endpoint respone looks like... we need to look into base64 + url encoding which is causing the wrong interpretation of the final url Commented Aug 3, 2015 at 15:09
  • @Ooker I'll take another look Commented Aug 3, 2015 at 15:09
  • @MarcGravell I agree the response is generic... i know you guys are super busy but please look into the response header .... like I said in the above comment Commented Aug 3, 2015 at 15:10
  • @HackerKarma <error><message>Image format not supported, or image is corrupt.</message>...; I'm checking something, though Commented Aug 3, 2015 at 15:20
  • @HackerKarma your comment isn't clear, but if you work for imgur ("we need to look into", etc), feel free to ping me at [email protected], and we can talk more - but I'm not going to dump the raw http (including keys, etc) here ;p Commented Aug 3, 2015 at 15:27
  • @MarcGravell Appreciated. If that's what imgur sending then they must be striping out all other data like "parameters:, request:, type:, method:, success:.... etc. I think we have to look into the "CONFIG" options that API gets.... base64 encoding ... Commented Aug 3, 2015 at 15:30
  • 1
    Let us continue this discussion in chat. Commented Aug 3, 2015 at 15:38
  • 1
    To confirm: looks like I am wrong and this is our fault; we should be able to fix it soon Commented Aug 3, 2015 at 15:40
  • 1
    @Ooker. No, I am not targeting you either. The official ♦ mod answer and upvotes, as far as my answer goes, and in general. How many of those upvoters do you think read my answer, comments, conversation with Marc. If they did then why am I left with 2 votes (excluding your's). That's why that joke but [status-completed] was my takeaway. But, since I worked so hard for this answer, I felt little sad to see your un-acceptance. And, that was it, nothing against you. You're fine. Comments are getting lengthy so its my last comment. Commented Aug 3, 2015 at 19:36