I use Xdebug on my development server and debug using PhpStorm in a page loading in Chrome. However, Chrome has the annoying feature to reload a page if it takes too long to load, launching another debug session on the page I'm already debugging.
I tried looking for a solution, this problem is an oldie, but the solutions posted then aren't applicable anymore.
I tried setting the Max. simultaneous connections to 1, but that causes other windows loading on the same dev server to halt completely until I'm done running the first debug session, so that's not an option for me either.
Is there any way to stop Chrome reloading pages when it 'thinks' the server in question is taking too long to answer?
Related
I am running my company's application locally and making some HTML/TS changes. However, whenever I save/hot reload and reload the browser, nothing changes.
I can stop debugging, build/rebuild, and run and the changes remain the same.
On a hunch I deleted the entire file from the directory and ran the application and nothing changed.
What am I missing here?
Web.Config is all configured to our dev environment currently, main web application is configured locally.
It turns out the problem was with Chrome. Inside Dev Tools -> Settings -> Network -> Disable cache (while DevTools is open).
When I clicked this option, it stopped caching old changes, and I was able to see my updates again with each hot reload.
On Linux Debian 10 (Buster), I am using the http(s) client google-chrome-stable.
I was configuring (nginx) and testing (chrome) a reverse proxy and it got cached using a wrong domain.
I fixed the configuration but it still resolve to the wrong domain.
I have tried to go chrome://net-internals/#dns and click on Clear host cache but that didn't change anything.
I have tried to go chrome://net-internals/#sockets and click on Flush socket pools but that didn't change anything.
I am not working with FireFox, so FireFox can resolve correctly (so does curl).
After about 10 minutes, without restarting chrome. I did F5 (refresh) and it was loading the proper page. I haven't found a manual way to immediatly clear chrome cache.
I am doing devops and I haven't solved this issue for years.
Would love to know how to do one day :O
What happens if you open developer console F12 and then hold down on the refresh button and then select empty cache and hard reload?
Take a look at this gif for an example.
Normal js code (no service worker, but the app has a manifest with an empty service worker).
A simple timeout to an ajax call that's the code.
I close all chrome tabs, I close the process in task manager, no more chrome processes and yet I still get requests on my server. This happens locally and on the server, I know this because I can see the cookies sent and for which user id is needed.
Also I know that chrome is running the code because there is a date in the request and is updated as it go.
Triple checked that chrome is closed on all users and all processed in task manager.
Is not a coincidence because at this moment I have 2 different users (different chrome profiles) doing this. Also in my dev server there are a lot of users with the same behaviour.
I'm also not sure is chrome, but has to be, node.js alone can't change the time of the request.
Win 10 and Chrome Version 60.0.3112.90 (Official Build) (64-bit)
Terrible and I don't know what to do...
if I restart my node.js server all the requests stops.
Was my mistake! As I have server side rendering (with react) I forgot that the timeout was also run on the server side. The fix was to don't run any timeouts on the server side.
Thanks anyway for the answers. I was concerned how chrome was still running my js code even shut down, made no sense at all!
The application is working on my Local Tomcat server. For some pages Firefox suspends, the status shows "Waiting for gg.google.com". The same page is easily achieved by Chrome.
Also, I need to mention that some icons with URLs on the Web page are not present in my server, so Firefox is losing time trying to get them
Yes, as Olaf Knock hinted, disabling JavaScript debugging in Firebug solved the problem. See https://briancaos.wordpress.com/2009/07/01/waiting-for-gg-google-com/
I'm developing an application that makes use of the struts2 framework, java and webcontent. I use Eclipse as my IDE and tomcat 7.0 as a server. Everything works fine, but when I make changes to the struts.xml file those changes aren't always reflected in my browser.
Here's my workflow:
1) Develop/make changes
2) save all
3) start tomcat 7.0 server
4) go to google chrome
5) go to localhost:8080/myWebapplication
6) test the application
What bothers me is that sometimes this works and new or changed actions are correctly displayed, while sometimes my application uses the previous sturts.xml and obviously my tests will fail. Why does my browser show this erratic behaviour? Do cookies, the browser cache or refreshing have anything to do with this? To be clear, I restart tomcat (after cleaning) and I restart my browser.
Restarting the browser is not enough to clear the cache.
This is a known Chrome issue, I suggest you to turn cache off while developing.
Read more on Disabling Chrome cache for website development.