Skip to content
This repository

Help with IE #1393

resistorsoftware opened this Issue June 19, 2012 · 7 comments

2 participants

David Lazar Julián F. Nuñez
David Lazar


My server process is accepting an image to upload. I am triggering a process that recognized an incoming IE request based on the redirect being present. I set the header to return 'text/plain', and I am redirecting to the URL...

client uploads on

redirect is set to and the server is dishing out the %s as an URL encoding string representing the image.

Things is, nothing is ever happening with IE... the browser never redirects... IE8 bombs out with an error about not being able to deal with the document body before blah blah blah... and IE... just nothing... is there some tip for getting IE to work??? what should I expect to be happening... ???

As it is... I watch my server dish out a 302 redirect to the page the client specifies, and then I watch IE just sit there? Does nothing... very frustrating... this is a simple CORS based file upload and while I appreciate the demo works... I am perplexed as to why a basic setup is so difficult to pull off. If the server sends a 302, IE should react to it and redirect. I see a lot of clients using IE, and all of them are getting effed-up by this issue.

Julián F. Nuñez

My suggestion would be: make absolutely sure IE is receiving the correct Location: header. Not just print what you are sending on the server side, use something like Wireshark to make sure things are reaching the browser correctly.


David Lazar

So... I have a crappy laptop with IE 9... what are the dev tools for that platform that are free and easy and would help debugging this. I know the 302 is hitting IE8 in my VM... I see the error in the debugger concerning IE choking on something...

When you say, be sure IE is receiving the 302... it is weird. The server is sending the 302. So why the hell would it not be received. It is just that it is ignored when received.

Site A uploads image to server B using iframe, server get hit, I see redirect param, and once image is saved server issues redirect as a response to the incoming POST.... so that is where the trouble lies. Clients are just getting a script that uploads and serves them no notice that it was all successful.. how do people deal with this??? The iframe should get the response and nicely inform the world all is well... right.. how does CORS affect that... does it?

Julián F. Nuñez

You are supposed to URL encode your response and put it in the %s part of the redirect param.

Then, you are supposed to send a redirect to code that looks like this:

That scripts grabs whatever is in filepath after ?, URLdecodes it, and puts it as the document body. The plugin then reads the document body, which is now what the original response would have been if you weren't using iframe transport.

David Lazar

The plugin then reads the document body, which is now what the original response would have been if you weren't using iframe transport.

I think that is the key... the way I am setting this up.. the plugin is failing to react to the redirect, hence nothing is happening... I will try and focus on that...

David Lazar

I am not getting the process of the plugin reading the document body of the redirect, which ostensibly contains the data needed to show off the uploads? What's the explanation for that?

David Lazar

I loaded up the demo code on my site to see what happens. It uploaded the image. Redirect seemed to do something now... IE8 reports Error Syntax Error : Syntax Error. That is progress I suppose. I also had to modify the redirect script to fire only after DOM loaded, anything before that caused a Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917) Anyway.. some progress in this...

David Lazar

Got the demo code working fine... therefore I will adapt to my needs. Thanks.

David Lazar resistorsoftware closed this June 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.