Comments on: Iframes / XMLHTTPRequest bug in Firefox

By: Tyron

Tyron — Sun, 27 Sep 2009 15:46:39 +0000

Thank you very much for your entry. I had a verrry similar problem while making my own multi-file-upload for my own CMS as well ^^
But blog entry ended my almost 2 hour search for a solution.

By: trying

trying — Sat, 24 Jan 2009 07:06:17 +0000

dear all,
how do i save the text written in an iframe to my servlet,for further b sent to the database…..i m a beginer in servlets,please help me with some example and syntax

thanks

By: Jakov

Jakov — Thu, 23 Oct 2008 17:58:54 +0000

Hi Stickman, it’s passed 3 years ago when you post this blog. Can you post your code here???

My English is very bad, and I can’t reed this at all..

I have same problem like was yours… from I must call XMLHttpRequest but you know what is happening… Thanks!

By: Stickman

Stickman — Mon, 11 Aug 2008 13:17:18 +0000

ilango: XMLHTTPRequest does not work between different domains. The browser will report any attempt to request a file from another domain using XMLHTTPRequest as a security violation.

By: ilango

ilango — Fri, 08 Aug 2008 14:38:12 +0000

I created web service using Rest.It works fine in a single machine.but access from different machines XMLHttpRequest.open(“GET”,”https://192.168.1.2/”,”true”) leave a exception “Access to restricted URI denied” security error.How to overcome it.please give the solution.

By: Draders

Draders — Thu, 27 Dec 2007 06:38:50 +0000

I am making an ajax cms for my company and set up my upload api similar to yours, I fixed the issue by adding a small delay before removing the iframe after its page has loaded.

setTimeout(function() { sickle.ajax._removeFrame(frame); }, 1);

_removeFrame : function(id) {
var tmp = [];
for (key in sickle.ajax.frames) {
if (key == id) {
var p = sickle.ajax.frames[key].parentNode;
p.removeChild(sickle.ajax.frames[key]);
}
else {
tmp[key] = sickle.ajax.frames[key];
}
}
sickle.ajax.frames = tmp;
}

By: Phzzy

Phzzy — Thu, 27 Dec 2007 03:23:21 +0000

you can use this:

function callback() {
setTimeout(“delay_ajax()” , 10);
}

function delay_ajax() {
// send XMLHTTPRequest
……
}

Phzzy

By: Alan

Alan — Sat, 08 Dec 2007 00:04:48 +0000

Yes Iframes can be a real pain when it comes to Firefox so on http://www.WebSiteTips.eu i resorted to Ifreames for IE and a frameset for firefox.

You will thin Microsoft would had sort the file upload stuff out by now and have a the option of using Ajax or maybe they do by now but i know few of the Ajax controls do quite what they say on the box.

By: Nathan

Nathan — Thu, 17 May 2007 17:38:00 +0000

Hey guys,
Don’t have time to read through everything but I did want to through this in. I am haveing the exact same issue. It sounds like the issue is that the XMLHTTP request is essential going out of scope ( or similar ) when the iframe is removed from the DOM. So when the request is returned from the server things are messed up. I have not tested this yet but I am working on a request manager that basically adds each new request to a queue and then executes them sequentially ( it is a lot more complicated but this is basically what happens ) I suspect that by passing the request data into the queue in the parent document the link between iframe and request is broken as the request manager creates the request not the iframe encapsulated code.

I will try to test this soon, if anyone beats me too it please post the results.

By: RghSx

RghSx — Mon, 07 May 2007 22:48:21 +0000

We had this same problem – we have a multiple upload file script that when submitted went to a hidden iframe that was generated by javascript. In the script that processes the file uploads we make some js callbacks ex(parent.document.getElementById(‘some_element’).value=”something”), including one call that performs some AJAX operations.

We solved this by removing the iframe from being generated by the javascript to be just a hidden frame on the main page. Apparently, there seemed to be a security issue with javascript generated iframes in firefox not allowing AJAX calls. Suffice it to say that all was fixed by moving the iframe out of the javascript.