I'm having an issue with FineUploader in IE11. My page works fine when I upload files after the initial load with no issues at all for any files. However, if I leave the page open for 5 minutes without any activity, the next time I try to upload a file, it fails. In the Developer Tools, all I see for the upload request is (Pending...) for protocol, method, and result. Sometimes, it will freeze the browser completely, but other times, it just says "Processing..." on the screen. This is a Ajax POST call. Any ideas?
The "processing..." message indicates that Fine Uploader is waiting for a response from your server after sending the last chunk of a chunked file. If Fine Uploader is stuck here, then your server is failing to return a response. This seems to be confirmed by your observations of the network request status in dev tools.
Sounds like an issue with your server, or perhaps some sort of browser plug-in. I'm not able to reproduce myself following your steps on IE11. Your next course of action is to look more closely at your server and how it is handling requests in this scenario. If you are seeing any error messages in the developer tools console that suggest Fine Uploader is at fault, please either comment here or open up an issue in the GitHub project's issue tracker.
Related
I am somewhat of a novice at debugging web traffic, so I am simply trying to understand what is going on.
I have fiddler and am using it to look at the network traffic being sent as I navigate to a specific website. I am noticing that the traffic picks up an HTTP 404 error thrown but I am still able to load the website.
Please help me understand how it still loads the website when it throws an HTTP 404 error? The error is never shown to the user. It is like it is ignoring it. I would think it would display the error to user and never load the website.
I have attached a picture of what I am seeing in Fiddler.
thanks
FiddlerTrafficwith404error
One of the reasons for this behavior is the browser stores the page in cache that is already loaded in browser once. Try opening the page in incognito/private mode (depending upon what your browser calls it) or try clearing your browser's cache and history.
I am using p:datatable and on clicking of row (Command link) I am displaying a panel. Most of the time it is working fine but in regression testing some time it is getting hanged but request is going to ManageBean fetching all the data.
But it is not rendering the panel. This error has no specific pattern. I have put log in all possible place even in phaselistner lifecycle everything looks good.
I checked in firebug response is also coming. from server
I am using weblogic 10.3.6,primefaces 3.5 and internet explorer 9.x
Try putting in a component in the page where the data table lives. This displays Ajax events and alot more. Then compare the log output for when it succeeds against the output for when it fails. This may point to DOM as was suggested or somewhere else.
I'm using Internet Explorer 7 and Firefox/15.0.1. I developed a web application in J2EE.
In application,if i click any hyperlink it is sending only one request in Firefox,chrome.
I checked it using Firebug and the logs also.
The same way i tested in IE7,It is showing 2 times logs for a single request.
Is it a bug in IE7? How to fix it?
Every time IE7 sending two requests.. Any tool to track the HTTP request?
You can install IE Developer Toolbar to debug JavaScript in IE
Mainly the problem with two forms i'm using...
that is a form with in other form. which caused IE to show exotic behaviour.
HTML is not well formatted. I changed it. it is working as expected.
When I'm using Firebug 1.5, I'm getting 200 ABORTED errors on certain ajax requests. You can see this happen on this demo page by typing into the textfield. The functionality of the site seems to work just fine even with these errors. Is it safe to simply ignore these errors?
This wicket mailing list thread seems to indicate that the wicket ajax code is doing what it should. Also, this firebug issue seems to indicate there may be some concern. Not sure what to think.
I just spent 30 mins with a similar problem. While this is not an answer directly to the above, a google search for my problem got me here, so I thought I'd add it here in case it saves someone else some time. As always, my problem turned out be developer error. I was binding an ajax request to a submit button, but I'd forgotten to use preventDefault() on the button before making the XHR, so the request was being aborted as soon as the default behaviour for the button kicked in - sometimes before the response came back, sometimes not - but it would always report in firebug 1.5 to be aborted.
I am also encountering this. I can see it on your demo site above on every request, but also I see it on one of my sites. I didn't notice this before, and I am sure I would notice it since I stare at the console for hours everyday. Gives some pretty mixed messages.
I am using a mac with firebug 1.5. This bug has been reported on the firebug bug list id=2712 but seems to be going nowhere. It's a tricky one. I tend to notice it when i have 2 simultaneous requests fired off at the same time, and perhaps one preemptively returns before the other. But this shouldn't cause an Abort message.
Sounds like aborts on requests that already were coming back with an OK. Firebug will filter these out on some future release, see the code change here:
http://code.google.com/p/fbug/source/detail?r=6127
I saw your demo page with firebug and seems to be working fine, there is no error to it and note that 200 response denotes that request went successful -> OK, it is not an error abort like you say. Thanks
I have a problem with ajax updater that i couldnt solve.
I have this code Servicii
It works perfectly in firefox but in internet explorer it does nothing.Also if i open the site from my harddrive it works but it only works for the link once then i have to reload the whole page...
Does anybody have an ideea on how to solve this problem?
Thank you
I've had this exact problem. I'm assuming that you've got a function which periodically makes a request to the server to fetch data then updates the page if that data has changed since the last time you made the request.
Internet Explorer will cache the results of Ajax calls to the same resource even if you tell it not to in your HTTP headers. So if you make a request to get_data?id=whatever over and over again, IE will make the request once and then stop making it in the future and simply return the result of the first request.
The solution is to add a dummy parameter to the request string. So first you request get_data?id=whatever&ie_hack=0 then get_data?id=whatever&ie_hack=1 etc. This will stop IE from caching the results and force it to make the request each time, since it sees a different query string for each request.
I also ran into a problem like this, not with caching but with race conditions. IE executed the render part of the function before the any data was returned. Here's the issue, and solution:
Returned AJAX html breaks IE click events