2
$\begingroup$

In order to improve this post, I was trying to add this picture(it doesn't load here either) to it ; but what I get is:"For security reasons, framing is not allowed; click OK to remove the frames." And then I'm redirected to another page with a big Oops in it.

What does this mean? I thought it might be because of the descriptions below the photo, so I removed them and tried again, without any success. Can anyone help me with this regard?

Update:

I will upload some pictures of the sequence of what happens:

enter image description here

enter image description here

enter image description here

enter image description here

$\endgroup$
  • $\begingroup$ Ah, I see what's going on now that you've posted screenshots. The framing issue has nothing to do with the image you're uploading - you should be able to reproduce the same issue with other images. It seems to be a bug in the Stack Exchange image uploader. Accordingly I've deleted my answer. $\endgroup$ – David Z Jul 15 '13 at 19:47
  • $\begingroup$ @DavidZaslavsky but you said you were able to upload the photo. $\endgroup$ – Ali Jul 15 '13 at 19:48
  • 1
    $\begingroup$ Though I will leave a mention that it's not appropriate to include that image in a Physics SE post unless you can verify that it is available under a Creative Commons-compatible license. $\endgroup$ – David Z Jul 15 '13 at 19:48
  • $\begingroup$ (2 comments up) yeah, that's how bugs are. They're very sensitive to the details of your computer setup. In this case it probably has something to do with which web browser you're using, so if you could edit details about your operating system (Ubuntu?) and web browser, including version numbers, into the question, that would help a lot. $\endgroup$ – David Z Jul 15 '13 at 19:50
  • $\begingroup$ @DavidZaslavsky I'm not sure how to do so, apparently the photo is from a contest held by NewScientist. How does one generally verify if such licenses exist? $\endgroup$ – Ali Jul 15 '13 at 19:52
  • $\begingroup$ I did some tests, there is clearly something fishy going on here. Normal images upload fine. That image doesn't. $\endgroup$ – Manishearth Jul 15 '13 at 19:52
  • $\begingroup$ @Manishearth (or Ali) did you try another animated GIF of comparable file size? $\endgroup$ – David Z Jul 15 '13 at 19:53
  • $\begingroup$ Just a note: repro'd on Chrome stable on Ubuntu 13.04. $\endgroup$ – Manishearth Jul 15 '13 at 19:53
  • $\begingroup$ @DavidZaslavsky I'm trying $\endgroup$ – Manishearth Jul 15 '13 at 19:53
  • $\begingroup$ Same here: Chromium browser; Version 28.0.1500.52 Ubuntu 13.04 (28.0.1500.52-0ubuntu1.13.04.3) $\endgroup$ – Ali Jul 15 '13 at 19:53
  • $\begingroup$ Other gifs work. I'm going to try pulling something off SSL. $\endgroup$ – Manishearth Jul 15 '13 at 19:54
  • $\begingroup$ @Ali Note: Chromium is not one of the supported browsers here. Note sure about Chrome Linux. $\endgroup$ – Manishearth Jul 15 '13 at 19:55
  • 1
    $\begingroup$ @Ali (8 comments up) Usually the web page you download the image from will state the license it is available under. Failing that, you could contact the copyright holder (probably New Scientist, but might be the person who created the image) and ask if they are willing to release it under a CC license, but in practice the chances of getting an affirmative answer are not good. If you don't see an explicit statement of the license, it is "all rights reserved" which means you can't upload it to SE. $\endgroup$ – David Z Jul 15 '13 at 19:56
  • $\begingroup$ OK, tried it with a normal GIF, an animated GIF, a normal image on SSL, an animated GIF on SSL. Both uploading from computer and using the link. All work fine. $\endgroup$ – Manishearth Jul 15 '13 at 19:58
  • $\begingroup$ To compare, the SSL animated gif I used was this one (my own creation) $\endgroup$ – Manishearth Jul 15 '13 at 19:58
2
$\begingroup$

Apparently it throws this exception on large animated GIFs. I took a screencap of a certain anime I'm watching and converted it to a GIF here. It's over 7 megabytes and gives the same error.

Chrome Stable on Ubuntu 13.04


For the record, this exception comes from a frame buster used to prevent clickjacking, CSRF, and the like. Basically, it prevents you from putting an SE site within an HTML frame on a different domain.

The image uploader does indeed use iframes, the response is delivered in a same-domain iframe which then calls a callback function in the parent frame1. However, being same-domain, that error should not get thrown.

I assume that the large image is breaking something, causing the inner page to seem to load on a different domain (abut:blank maybe, that's what it looks like)

1. I'm not entirely sure why they haven't used a simple POST request here, but they probably have their reasons.

$\endgroup$
  • $\begingroup$ Is the footnote aiming at me? $\endgroup$ – Ali Jul 16 '13 at 5:46
  • 1
    $\begingroup$ @Ali No, by "they" I mean "developers". A few months back I had been trying to reverse-engineer the image upload for a userscript I was writing, and I discovered that they used framing to make it work. I don't see why it can't be done without framing, that's all. Again, they probably have good reasons. $\endgroup$ – Manishearth Jul 16 '13 at 5:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .