Is it possible to show only 400 errors (or all errors) in the Firefox browser console?
There are usually a few hundred requests in a typical web page, most with 200 (OK) status. It'd save time by filtering those out to only display errors (400, 404, 403, 500 etc) which require investigation.
I know it is possible to sort by the Status column but filtering by Status number would be better in many cases.
(Chrome once had such a filter but it no longer seems to exist).
Related
I have an Electron application that uses Kibana iframes in it. I am using a splash screen to wait for Kibana before showing my program interface, so that user will not see the "Kibana server not ready yet" text. I am trying to send GET request to "http://localhost:5601/status" to check if it returns 200 as status code. Doing this in a loop until I get 200 response and when I got the 200 code I close splash screen and show my program interface. However Kibana iframes still shows Kibana server not ready yet error. What is the reason behind this? Is there any other API URL that I can check to determine Kibana is completely ready? Please help
There is no 200 in the response. I think you are looking at whether the call to http://localhost:5601/status was successful which returns a 200. which means Kibana is up but probalbly not ready yet or is "warming up"
However, you should capture the response and make sure the overall status is green
This also sends statuses which shows status of each individual plugin, so if you dont care about certain plugin, you can iterate and check status only for required plugins.
In Chrome Developer Tools, I'm getting a 500 error in the Console tab, for a GET request:
But in the Network tab, I don't see that request; I only see a POST request for the same page, with a 200 status:
Shouldn't I be seeing the SplitShip.aspx GET request in the Network tab?
Shouldn't I be seeing the SplitShip.aspx GET request in the Network tab?
You should of course, but maybe this request has been made using an AJAX call or something. So make sure you apply proper filter to your Network tab by selecting All:
This way Chrome will show All requests being sent to the server, including XHR ones. Are you seeing the smoking gun now?
Via Firefox, if I do a GET text/html request to my web app, I get a 200 response back, and then Firefox sends 3 more of the same request right afterward. All return 200s. Does anyone know what would cause this?
*Some other observations about the issue:
In Firebug's network tab, only one request shows up. I can only see the extra requests using Tamper Data or another tool that sees the Http requests sent from my browser.
This issue does not happen in prior versions of my web app. When I compare the responses that get returned by the two different versions of the web app, I can't see anything that would cause this issue (but then, I really don't know what to look for). The responses are identical except for the web app's cookies, which are different.
This issue happens with JavaScript enabled or disabled.
Something similar is happening with Chrome, though it seems to be sending only 2 extra requests.
I don't see any browser redirects in the Html header.
This is only happening with text/html requests, not css requests, for example.
All 4 responses returned seem to have the complete Html page in the body, and they also have the cookie that the web app uses.
In Tamper Data, the 'Load Flags' column (whatever that is) says the following: First request is VALIDATE_ALWAYS_LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI; second and third requests are LOAD_NORMAL; fourth request is LOAD_FROM_CACHE VALIDATE_NEVER
I don't see it happening with POSTs
It does not happen when the response is a 302.
If I go into the firefox config and set network.http.max-connections-per-server to 1, then Firefox only sends one request (the issue does not occur). (I don't think I can ask all our users to do that. :-))
*Why this issue is a problem:
This site has been around a long time and wasn't designed for this behavior. It's probably not going to go well.
(edited to add new findings)
I'm trying to debug a performance problem in IE9, but have problems understanding what the developer tools try to tell me. I use IE because the problem does not appear in other browsers.
I see huge times categorized as "Start", i.e. before "Request" and "Response". Note that "Start" is the term used in my German version of the IE, I hope it is the same term in English as well.
"Start" takes about 2-20sec while the actual "Request" and "Response" are well below 100ms.
What does the IE do during this time? What might be the reason for this?
The receiving side of the requests (IBM Webseal) seems to see the requests only after the "Start" time has passed.
Some more background:
We have a little web application which has reasonable performance in most configurations. Authentication for the application is done through an IBM Webseal.
This just works for Firefox. This also works for IE9 when authenticated via username+password or RSA Token, but it is extremely slow when authentication happens based on PKI cards in IE9.
In F12's network tool the times refer too:
Start - The time from when the request was initially created to when the request is sent. There can be a delay here if the max number of connections to a server is exceed at the request gets queued.
Request - Time to first byte. The time taken to send the request and receive the first response from the server.
Response - The time taken to receive the response data from the server.
If you go to the timings tab in the tool and click on any of the timings like 'start' you'll get a brief description of it in the bottom right.
I am trying to optimise Magento for SEO. I have it included in Google Webmaster Tools, and I have noticed that there are a lot of pages that are labelled withing GWT as server errors, that is, mostly http 500 errors.
So I did some looking into it, and the URLS that google says are HTTP 500 errors, well, I dont think they are supposed to be. Reason I say this is because Magento is calling the 404.phtml template of “Whoops...."… but Google is right, the header sent is http 500.
How do I go about debugging this? Any ideas?
Many thanks for your help!
Ben
Try visiting the offending pages with a browser that can emulate Googlebot headers (e.g. Firefox with User Agent switcher). This will ensure that the site is responding with the same response that Google is seeing. Also, you will need to enable developer mode and enable error reporting, which you may want to do conditionally based on your IP - this can all be done in index.php.
Ensure that you are reviewing the server logs.