While using Firefox network panel I noticed that it shows only "http://" requests in its panel whereas chrome shows all (images, css, js,....).
Is there any way to enable local requests monitoring in Firefox network panel..
Thanks in advance
This is not currently possible, and is being tracked in Bug 1000540.
For local testing, consider working around this bug by running a local HTTP server. If you have Python installed, you can run python -m SimpleHTTPServer to serve the current directory over port 8000.
Related
I am using Puppeteer along a proxy service, and after getting unexplainable high bandwidth usage I used a local proxy server to monitor the requests that were generating this bandwidth. I discovered that almost 90% of the traffic was used to request some crx files/updates.
My project requires me to open a a few thousand browsers every hour, in order to keep each task with it's own cookies and proxy. Every Chromium browser I open will eventually download ~10-15MB of files, using the proxy that is passed as arg to puppeteer.launch.
puppeteer.launch({
headless: false,
args: [
`--proxy-server=http://${this.proxy.host}:${this.proxy.port}`
]
)}
This requests do not appear in the network section of devtools and cannot be intercepted using:
await page.setRequestInterception(true);
this.page.on("request", cb);
I started a local proxy server and gave it to puppeteer via launch args to use, in order to monitor the requests made through it by Chrome. This is how I found out about this downloads. I blocked the first domain that Chromium was using to download these crx files, but Chromium started to download them from another domain, and so on. Some of this domains and URLs are:
http://redirector.gvt1.com/edgedl/chromewebstore/L2Nocm9tZV9leHRlbnNpb24vYmxvYnMvYjFkQUFWdmlaXy12MHFUTGhWQUViMUVlUQ/0.57.44.2492_hnimpnehoodheedghdeeijklkeaacbdc.crx
http://dl.google.com/chromewebstore/L2Nocm9tZV9leHRlbnNpb24vYmxvYnMvYjFkQUFWdmlaXy12MHFUTGhWQUVi
https://google.com/dl/something/something.crx
There were even more. When I block one domain, puppeteer finds another. This files are getting downloaded for every new browser launched, using expensive proxy bandwidth.
Is there a way to stop these downloads, or at least make Chromium only download them once? Not for every new browser launched. Can I at least instruct chrome to download these files without using the proxy?
This happens for both v5.5.0 and v8.0.0.
After a lot of time trying to find what is this extension that chrome always has to download, I found out about Chromium Components, that can be inspected using chrome://components. Looks like these are also shipped as crx files.
In my particular case Chrome was downloading "pnacl". The only way I was able to find this is by recognising the version number from the first link that I posted in my question (0.57.44.2492). Using chrome://components in a browser instance launched by puppeteer with the headless option to false, I found that pnacl had the exact same version.
I was able to prevent Chrome from downloading this component using the flag --disable-component-update. This flag is used by default by some webdrivers but not by the one that puppeteer (v5.5.0 or v8.0.0) downloads.
If anybody else encounters this problem, yours may be related to an extension instead of a component, so you may need to also use a flag to disable extension updates, but there is none, so I use --disable-extensions and --disable-default-apps just to make sure.
Browserstack has discontinued its chrome extension for local app testing and has moved to a desktop app/.exe that you have to download to do local testing.
I can't seem to get this working running Windows 10 and I'm wondering if anyone else has had this problem and resolved it.
When I download and execute their desktop app, it tells me local testing is enabled:
https://imgur.com/a/2ey7N3U
When I then use Browserstack Live to test local development I get an error message saying local testing is not enabled and it gives me the option to download their desktop app, which I have and says local testing is enabled:
https://imgur.com/a/YMd0LOj
I have tried uninstalling and reinstalling the desktop app/.exe, it gives me the same results.
I've confirmed with our network team that I am not behind a proxy which is an option to manage the desktop app (under "advanced settings" in the first screenshot above).
Our network team has also whitelisted all traffic from (asterisk).browserstack.com (the actual asterisk character is stripped here) and they're telling me "Additionally I watched his traffic on the firewall as he tried to use the browserstack software and no traffic was blocked
I've also been in contact with browserstack support but have basically been feeding their responses to our network team and our network team's responses back to browserstack. At the end of the day, I still can't get local testing working.
Does anyone have any ideas what might be happening and how I can resolve it?
I encountered the same behavior while setting up Local Testing with the BrowserStack Local Desktop app that was released after the announcement by Google about the end of support for Chrome apps (Click here). However, I was able to set-up Local Testing post configuring the proxy server details as mentioned over here.
I would suggest checking with your IT team if traffic for *.browserstack.com is being routed via a specific proxy at your end and configuring the proxy details in the 'Advanced Settings' for the desktop app.
In case this doesn't work, do contact BrowserStack Support
I am working on an iOS app that connects to a web service. For development and testing, we use Bonjour to find servers on the local network, and during sign-in the app offers to connect to one of them instead of the production site.
Since upgrading to El Capitan, I am unable to connect from the Simulator to a web server running on the same Mac. I am able to reproduce this issue using Simulated Mobile Safari and the web server that comes with the stock Python in OS X.
Open Terminal, start a web server: python -m SimpleHTTPServer 8000
Open Safari inside the Simulator, enter URL: http://my-computer-name.local.:8000/
Simulated Mobile Safari displays "Safari cannot open the page because it could not connect to the server."
Additionally, the following message appears in the Console each time I try to load the URL:
assertiond[____]: assertion failed: 15A284 13A340: assertiond + 13207 [28CC4371-F3F9-3578-9436-310B23A2C638]: 0x1
Other possibly relevant facts:
Desktop Safari is able to connect using the URL http://my-computer-name.local.:8000/
Real Mobile Safari (on an iOS device on the same network) is able to connect using the URL http://my-computer-name.local.:8000/
Simulated Mobile Safari is able to connect using the URL http://127.0.0.1:8000/ (I need it to work with the Bonjour provided hostname, though).
Simulated Mobile Safari is able to connect to another machine with an URL like http://other-computer.local.:8000/
I'm using Simulator Version 9.0 (SimulatorApp-620 CoreSimulator-179)
OS X El Capitan 10.11 (15A284)
Amusingly, searching the web for the UUID 28CC4371-F3F9-3578-9436-310B23A2C638 yields only a handful of job posts. (You can make $15 for fixing this bug!)
This does not appear to be related to App Transport Security. My app behaves this way when ATS is disabled.
Are you able to reproduce this problem? Am I missing something?
I worked the issue around by adding an entry to the local OSX /etc/hosts file:
Append your FQDN after "localhost":
127.0.0.1 localhost mymachine.mydomain.local
Here's my situation: I have two computers on my desk and I would like to use one of them to develop webpages and use another to do a live preview.
Is there an option in Brackets that I can do this? I tried to access the intranet ip address with the port number appearing in the URL when I'm doing a live preview using a local machine, but it cannot be accessed.
There is currently no remote (LAN) live preview in Brackets and there are open issues on Github for the feature request. (Here's one for example)
The livedev.multibrowser option described in the currently accepted answer opens live preview to multiple browsers on the same machine but does not allow access from anything other than localhost.
Here's a workaround that I've been using in the meantime:
Make a standard local web server (with Node/Apache/IIS/whatever) and install and run LiveReload on your dev machine for your project. On the remote machine(s) install the LiveReload browser extension, visit your site and turn on the LiveReload plugin. You don't get the instant (saveless) updates of the Brackets live preview, but the page will auto-refresh on remote machines when you save any files inside your project.
It is possible to use Live Preview on different machines that share the same local network since Release Brackets 1.1. To do this, open your preference file via Debug > Open Preferences File and insert the following directive: livedev.multibrowser: true. Note that you may have to add a trailing comma. For more information, see https://github.com/adobe/brackets/wiki/Live-Preview-Multibrowser
When I yesterday returned to Visual Web Developer I was no longer able to run/debug my projects. Clicking the green play button launches ASP.NET Development Server (and it shows up in the systray) but the browser only shows the error message "Firefox is not able to connect to localhost:58127" (translated from Swedish). IE7 says "Cannot show web page".
I cannot figure out why this happens. It worked a couple of weeks back. Could there be a Windows setting that mess things up? (I've tried to disable the firewall without any change.)
Are you using Vista? I've had the same issues with recent Vista updates.
Firstly, make sure Visual Studio is running "As Administrator".
Secondly, when the browser launches, replace "http://localhost:" with "http://127.0.0.1:". If that works, then its because a Windows Update messed up your hosts file.
If this is the case, make sure you hosts file has this line in it, uncommented: "127.0.0.1 localhost"
my hosts file is in this directory: "C:\Windows\System32\drivers\etc"
yours will be something similar to that.
Are you perhaps using NOD32 or any other antivirus that may cause problems?
I encountered this issue today and just wanted to elaborate because my hosts file had "127.0.0.1 localhost" already defined.
I was able to see the default IIS site by referencing localhost but when I tried debugging in my IDE it would always display "cannot display webpage" in IE and "Oops! Google Chrome cannot connect to localhost" in Chrome.
I opened a command prompt and typed "netstat -a" and reviewed the results. I saw that my port used by my debugging web server was listed as "LISTENING" on the local address of [::1] only:
TCP [::1]:64212 [ComputerName]:0 LISTENING
What's unusual to me is that debugging worked for a period of time and then it seemed like all of a sudden it stopped. The first couple times it happened I re-installed Visual Web Developer Express 2010. This became rather annoying because it was a long process and the problem continued to resurface after what seemed to be an arbitrary period of time.
This latest time I changed my hosts file to include "::1 localhost" (the opposite of this solution and numerous others I found online) and that has resolved my issues with my debugging environment.
I'm grateful this resolved my issue but am still curious as to why and how my debugging environment seems to change. Additionally, I'm curious why there are multiple loopback addresses other than 127.0.0.1. Is "::1" an ip6 standard? If so, shouldn't localhost be routing to 127.0.0.1 and interpreted by the tcp/ip stack as the same as ::1?
I had this problem with Visual Studio 2013. I have set the Firewall system manually. This means that, at the time of communication by programs Firewall notify me. Incorrectly linked to "devenv.exe" was blocked by the Firewall. Correct mode of communication "devenv.exe" will solve the problem. in your case cheeck Firewall options and filtered communications.