I've got this weird bug. The progress bar in IE's bottom-window status bar keeps incrementing very slowly after an Ajax POST. At least that's where I think the problem is.
How can I tell what the hell IE is doing that's causing the progress bar to keep going? In FireFox, I would just look at the Console tab in FireBug and see what's up.
I turned Fiddler on but it doesn't pick up any HTTP requests or responses being sent.
What can I do in IE?
I'm not very experienced in Web debugging but you might try the Developer Tools that come in Internet Explorer 8. It's under the Tools menu, or just hit F12. I think the Profiler tab may be helpful. I had heard somewhere that the IE8 Tools were created to mimic Firebug's feature set as closely as possible.
An another tool for checking HTTP requests is the Debugbar
This might not help if Fiddler isn't picking anything up, but HttpWatch is a great http request debugging tool for IE.
I don't think there is a problem here, earnestly. IE has a bug where it shows that a request has not yet been completed when it has. This has been around for a while now, and I have tested my own applications against it. There is nothing happening and there are no connections waiting for a response, yet the browser still thinks there is an open connection.
i recently discovered this tool for earlier IE versions which can be used in combination with the IE debugger for network profiling and more behind the scenes debugging
http://www.ieinspector.com/httpanalyzer/
open IE ...thn press F12 ...here you will get many menus..to debug script choose "SCRIPT" option..and start debug...and if there is any error on page...thn u will get on Console option..also see on attach image...
Related
I'm using "Firefox Developers Tools" to debug my webapps. The tab Network Monitor show all request, and in each one I can see Headers, Cookies, Responses, Timing but the Preview tab not show the content, it's always empty, else even when the Response (from server) is an html.
Who ever happened something similar?
Apparently only HTTPS sourced pages are rendered in preview. I am figuring out how to resolve this for local development for one week now. Dont want to port back to Chrome couse it is really slow but if i cant resolve this ... will have to.
Firefox runs my website significantly slower than IE or chrome. When I check the network tab, I see that 235ms is spent blocking. No blocking is reported for my site in chrome, and no blocking is reported in firefox for other sites, like google or amazon. It also has a much higher receiving time than chrome.
Its my understanding that blocking occurs because the browser has a limited number of connection that it can make:
What is meaning of 'Blocking' in Firebug Net Panel?
Here's an example of a website blocking before the document: http://thehill.com/ (sorry in advance for the politics). The blocking on this site doesn't always occur (it does on my site) and is about 1/10th the length of the blocking on my site.
Shouldn't the browser always have all its connections available when it tries to download the Document? Why would firefox be blocking on the document and not chrome, and how can I fix it?
Firefox has it's own http proxy settings. IE and chrome take proxy settings from windows settings. Please check if there is some difference between your FF and IE settings.
Next thing you can do is creating new, fresh profile in FF (make sure there is no addons installed) and trying again.
try making your javascript calls asynchronous. My wild guess (with no codes provided that is the only thing possible) is that you have some javascript call that is blocking. try optimizing and debugging javascript, maybe that will help you see where did the blocking appear.
When I open a site the loading spinner keeps spinning in the favicon area and I see the 'waiting for site.com' message.
It seems to me like the site has already fully loaded, but evidently not.
How do I check what's still loading?
I'm happy to use Firebug as well if it's easier to see there.
Edit:
Network tab doesn't indicate anything is still loading.
Edit: is there any way to filter network tab to see what's still incomplete vs already completed requests
You can use developer tools (Network tab) for this analysis.
To check what's still loading, first open the Developer Tools (press F12) and switch to the Network tab. Then load the site; you'll see all the requests the page makes. From there, you'll be able to see which aren't yet done.
I'm facing a very weird kind of problem while running my application.
When I hit a website and login to my application, the POST is getting converted to GET automatically. Since all the request parameters are getting lost due to this, the page shows up an error screen.
This issue happens in IE-8 (Windows 7), but works absolutely fine in IE-8(Windows XP).
How is the OS involved in this? Have anyone faced such issues? This issue happens in IE-9 as well.
Kindly refer to this issue as well. Any solutions would be really helpful.
Thanks !!
This issue was happening due to a security setting in IE in Windows 7.
There is an option of Enabling/Disabling protected mode in IE of Windows-7. This is a new feature present in IE of Vista/Windows-7 and this option is enabled by default for “Internet” zone and “Local Intranet” zone(or any one of them). Disabling at these 2 places solved the issue.
Tools -> Internet Options -> Security -> Internet/Local Intranet -> Uncheck on the "Enable protected mode" option.
I'm a bit late to this party, but I just ran into this as well, and it made me crazy. IE (only) was turning a POST into a GET, which took running Fiddler to determine. This thread got me part way there, but the protected mode wasn't the deal. It turns out one site was in the Internet zone (the page making the post) and the other (receiving the post) was in the Intranet Zone. By adding the calling page to either Intranet Zone or Trusted Sites, IE stopped turning the POST into a GET. It appears that you can't call up the zone stack without IE turning the POST into a get, but you can call down. The big tip for us (we opened the POST in a new window (target=_blank)) was that when calling from Internet to Intranet, the new page opened in a new IE window, but when configured "correctly", the new popup will open in a new tab (the expected behavior).
Using Firebug v1.20b7 with Firefox v3.0.1 I use firebug a lot for web devlopment.
I have very often the problem that Firebug won't show its web console for seeing the POSTs and GETs. I can view all the other tabs, including the NET tab that gives me a lot of the same information that the CONSOLE tab does.
Curious if anyone else has had this problem, and maybe a solution, or maybe this is a bug of Firebug.
There is a limitation in firebug (or rather, in firefox iteself), which will be fixed in one of the newer Firefox releases.
The bug is caused by the fact that firebug needs to send data a second time to monitor what's going on in the connection.
There's now a special API hook in the firefox trunk that should prevent this workaround in the future, so that firebug can really spy on what's going on :)
Well, 1.20b7 is technically a beta version of Firebug. :)
I've had problems with certain features off and on, but a restart of Firefox seems to fix it more often than not.