So I have this problem when I click on someting in a web App which sends an ajax request and then I immediately click on ANOTHER TAB in Firefox (a tab with a completely different webpage) and if I go back to the original my script stopped working and Firebug doesn't show the requests anymore.
Is this a Firebug related problem or do I need to worry about production mode as well?
Does anyone ever have similar?
I heard Firebug used to have problems with other extensions and websites
Related
In Firefox, I use Firebug which allows me to view every http request my ajax calls are making. I've switched over my development to Chrome and am liking it so far. My only complaint, however, is that the developer tools don't seem to allow you to view each ajax request. I've had it happen once where the Resources panel showed multiple requests to the same resource, but it's only done it once and never again.
Is there a way to reliably see every http request that a page is making through javascript from within Chrome?
[Edit:11/30/09 11:55]
Currently, to get around this, I'm running Fiddler next to Chrome to view my requests, but if there's a way to do it from within the browser, I'd prefer that.
I know this is an old thread but I thought I would chime in.
Chrome currently has a solution built in.
Use CTRL+SHIFT+I (or navigate to Current Page Control > Developer > Developer Tools. In the newer versions of Chrome, click the Wrench icon > Tools > Developer Tools.) to enable the Developer Tools.
From within the developer tools click on the Network button. If it isn't already, enable it for the session or always.
Click the "XHR" sub-button.
Initiate an AJAX call.
You will see items begin to show up in the left column under "Resources".
Click the resource and there are 2 tabs showing the headers and return content.
The most up-to-date answer to this is: they are listed under the 'Network' button in the developer tools, no longer under 'Resources' like it used to be.
Update
Chrome changed how to inspect requests and suggests now to use the Catapult Netlog Viewer with the logs exported from chrome://net-export/
chrome://net-export/
More Info
Old Chrome Versions
You also may use this link in Chrome for more detailed information than the inspector did it.
chrome://net-internals/#events
This shows the log of all requests of the browser while open
don't know as of which chrome version this is available, but i found a setting 'Console - Log XMLHttpRequests' (clicking on the icon in the bottom right corner of developer tools in chrome on mac)
Open up your DevTools and press F1 to access the settings. Look for the console section and check the checkbox for "Log XMLHttpRequests".
Now all of your ajax and other similar requests will be logged in the console.
I prefer this method because it usually allows me to see everything that I'm looking for in the console without having to go to the network tab.
You could use Fiddler which is a good free tool.
Thanks all person who try to help in this post
I have ubuntu 13.10 and my chrome version is 34.0
For my situation this works
1.open developer tools in chrome(or use right click on your page and then select inspect element)
2.go to "Network" tab
3.find your ajax request in "Name Path" column
4.click on the specific ajax link
now you should see a new Panel in front of you request
in this panel select "Response" tab
In the step 5 of Phil, "Resources" is no longer available in the new version of the Chrome. You need to click the page icon just beside the Ajax page listed in the bottom pane with the columns of Name, Method, Status, ...
Then it will show you more panels where you will find the error messages.
You can also just right click on the page in the browser and select "Inspect Element" to bring up the developer tools.
https://developer.chrome.com/devtools
How can we detect through PHP or maybe in node.js or other languages if a web page crashed (without the browser EXITing) so that when a user press the "reload" button on the "Aw Snap" page in chrome certain specific content inside the page can be shown in this particular case (crash case).
In a crash without EXIT, a browser shows per example in Google Chrome the famous "Aw, Snap!" page.
I don't want to know how to capture if the user refreshed the page or the page reloaded which can be known quite easily with different methods [one example see this PHP this code which can detect if users refreshed the page on major desktop/mobile browsers except IE unfortunately this code does not capture a crash event and the fact that user might request again the same page after a crash.
I tried using "register_shutdown_function", and some other maneuvers using connection PHP functions like "connection_aborted" etc... but with no success. I figure out a sloppy way through the use of session variables but probably there are better clever manoeuvres.
Any help or suggestion would be greatly appreciated. Any solution in nodejs will be also welcomed.
web brower crash because too many process from your browser to PC of Client.
this crash can't detected by php because PHP server scripting. and you have question.., why not use JS for detect crash of browser?, because JS created just for controller website,. if you force to checked that use ajax, node, etc you can't do that, why? because the problem comes suddenly
and detected crash browser from php is impossible.
I've got a web form (using the ZK framework), let's say at http://www.example.com/myform
This form get's included in my main page (for example http://www.anotherexample.com) in an iframe.
Now the strange thing:
In Internet Explorer 9-11, the IFrame completely reloads whenever I unfocus a field (some field checking happens there). But this ONLY happens in IE and ONLY in the IFrame. If I load the http://www.example.com/myform directly, it works fine.
Another detail that makes the whole thing strange is: If I addtionally open a tab in the IE and load http://www.example.com/myform there, the iframe suddenly also works fine (after one reload).
Unfortunately, IE does not display any errors when reloading the iframe, so I have no clue what happens and why. Other browsers (Firefox, Chrome) work perfectly fine with the IFrame.
Any clues what might be the reason there?
In this case, the reason was P3P, as described here: https://blogs.msdn.microsoft.com/ieinternals/2013/09/17/a-quick-look-at-p3p/
In short, Internet Explorer rejects cookies from third-party contexts (different domain) in iframes, etc. This of course leads to the behavior mentioned:
Any request (including something that triggers on "focus lost") sent to the ZK backend will not have a session id (because no cookie), so ZK will trigger a complete reload.
Opening the ZK application in another tab allows it to create a cookie - which then the ZK application inside the iframe can access
The solution is to send the correct P3P header, in ZK this can be done in various ways, for example via the .zul file header directive, in a servlet filter or directly on the webserver. Having done this, the application works as expected in IE 9-11.
I'm working on an angular application and came across the bug that in Firefox, if we refresh quickly enough (often takes several times) the page will eventually fail to load and, in my case, displays an HTTP 0 error code, which if I'm not mistaken means that an AJAX call was canceled before receiving the response from the server.
I have not seen this behavior in Chrome or IE, but I don't know if that's because the JS engines in those browsers are helping me out, or if it's a browser bug itself (in Chrome at least it appears that the refresh button for a page is disabled while requests are being made on page load).
Is there a Firefox bug, an angular bug, or a bug in my application? If it's the later, how can I avoid this?
I'm working on developing a site on my local machine (Windows 7 Ultimate x64) using WAMP, running APACHE v2.2.22, PHP 5.3.13, and MySQL v5.5.24. I'm developing using Chrome v 22.0.1229.94. I've got quite a bit of javascript in the site, however, and Chrome is relentlessly blocking javascript from running on the page.
Clicking on the little 'blocked javascript on this page' icon in the address bar includes the dropdown that has "Always allow Javascript on Localhost" checked off, and I also have a JavaScript exception in Chrome's settings explicitly saying to always allow JavaScript on 'http://localhost'.
Cookies are being allowed, "Allow all sites to run JavaScript" is checked off, and I have no idea as to why Chrome is not allowing the JavaScript to run.
Overall, it's not imperative to the project that I figure out a fix as both IE9 and Firefox 16.1 are allowing JavaScript and I can utilize them. I am simply curious if there's anything I can do to fix this in Chrome, as I would like to continue developing in Chrome.
If you notice that JavaScript is only blocked when the console is open (as some are saying), chances are that you disabled JavaScript in the console settings.
Open the console.
Click the vertical ellipsis icon (or the gear icon on older versions) in the upper right and go to settings.
See if the "Disable JavaScript" checkbox is checked.
I have the same issue, but only when the console is open. When the console is closed, JavaScript loads fine on localhost. Makes it hard to debug things though....
I got around it by opening localhost in an incognito window.
You can give your local server a domain name, may be that would help.
Open C:\Windows\System32\drivers\etc\hosts in notepad
Edit that file add a new line at the end
127.0.0.1 mydomain.com
Save, now goto chrome and type in http://mydomain.com/ this should point to your local server.
Since you nolonger run on "localhost" may be chrome will let you pass.
Let's me know if that works. Good luck!