I used "map remote" in Charles 4.2.1 using a proxy to an iPhone SE iOS9.3.2. After doing what I had to do, I removed the "map remote" with not success.
The URL is still mapped to a remote URL and it is frustrating as I can't any longer go to the actual URL.
So far, I tried:
removing the map through tools > map remote.
removing ALL maps through tools > map remote.
uncheck the "enable map remote" in tools > map remote.
remove the proxy + quit Charles + restart the device.
Nothing seems to help, it is like the URL is forever bound to the new URL.
So, is there a way to fully reset/restore/clear/clean any remote mappings created with Charles, other than the obvious tools > map remote?
CharlesProxy acts as a proxy when performing remote maps (instead of sending 301 to your browser that would be cached), so I guess the only reasonable explanation to your issue is that your browser has cached the URL's content.
Have you tried clearing your phone's browser cache?
Related
In FireFox I load my web application which has a Source Map. The Source Map seems to be loaded correctly, as the Debugger tab shows the original source files.
However, the Console tab contains only links to the compiled code, instead of the Source Map code.
Is a Source mapping done in FireFox Console?
Do I have to enable anything?
Update: I also tried it in chrome and there the console shows the original location of the event, BUT: only the first time after starting chrome AND only, if I first load the page and then open the developer tools. Exactly same behaviour in opera (same engine...)
Update 2:
As of Firefox bug 670002 Web console does still not support source mapping.
In chrome the source mapping works more than once if I directly embed the source mapping instead of using an URL.
For chrome developer tools, the answer was covered in this issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=633549
In some cases, developer tools requested the source map file when no connection was alive anymore. It tried to open a new connection, which failed silently because of an invalid ssl certificate.
You may run into this, when:
You serve using https
You do not have a valid ssl certificate (which may happen often when you just run a quick local node.js https server)
Your https server closes the connection fast or immediately
Especially when your https server sends connection:close in the response headers you may run into this.
The biggest issue is, that this request is not shown in the network tap nor in the console, it is just silent.
On GitHub Desktop (I use it on Windows), I have had this error over the last few days:
My Internet connection seems to work fine though. What could cause the issue?
Is your internet connection goes through firewall/proxy server. I found that GitHub Windows client is only reliably works when no proxy enabled. Being windows (.NET to be precise) application it takes proxy settings as they defined in Internet Explorer connection settings. Meanwhile, Git itself, which GitHub Windows client desktop application simply uses via command prompt, is governed by http and https proxy settings in .gitconfig file or environment variables. This discrepancy makes it quite sophisticated to setup.
What's interesting, is that desktop app was working the first time I installed it fresh (never had it on this Windows), but it wasn't able to connect to GitHub. Then I started to fiddle with --global http/https settings and I broke the app. Now, even uninstalling and installing it back again, I still have connectivity issues, as it seems to remember settings somewhere, as it doesn't prompt me with welcome screen and does remember my name.
Worth to mention, that even if the app complains about connection, I can clone the repo with it.
This worked for me:
In Internet Explorer: Tools/Internet Options/Connections/LAN Settings
Uncheck "Use a Proxy server..."
Restart GitHub.
You might also be able to disable the Proxy Server via Edge. In my case, I found that after turning it off in IE, it was off in Edge also.
Edit: I also had to update the GitHub application in order to be able to clone to my local repository.
i am only start learning GWT by following their tutorial on https://developers.google.com/web-toolkit/doc/2.1/tutorial/create
On that page, when i reach the heading Running the development mode code server (from Eclipse), i copied the generated url http://127.0.0.1:8888/StockWatcher.html?gwt.codesvr=127.0.0.1:9997 to my browser.
It eventually times out, says page not loading...the plugin page did not show up initially, so i manually installed the plugin...but it still times out...
On the screen, it says...
===============================================================================
The connection was reset
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web
==============================================================================
Am i missing any configurations etc?
Thanks very much in advance
It still looks like your browser is missing the GWT developer plugin. Try a different browser (preferably Chrome). You can also check the instalation of GWT in Eclipse. Look into Windows/Preferences and under Google/WebToolkit you should see checked GWT SDK. Also you can check if a jetty server runs on port 8888, when you type "netstat -na" on the command line.
I'm experiencing some weird problems on using web stuff in Eclipse (Indigo, Indigo SR2 and Juno). My proxy configurations seems to be messed when Eclipse tries to do sth on web.
My browsers stop to communicate and I have to restart my machine in order to restore my Internet access again (or close Eclipse and browser and force the browser to reload proxy configurations). In Eclipse, the communication is unstable, working/not working sometimes.
My "NetWork Connections" are set to Manual, where proxy address, port, auth, user and passord are set to HTTP and HTTPS schemas (I didn't use it for SOCKS due to update issues - see this question).
I have no idea of what is happening and why, and how to fix it. Thanks for helping.
It is very unlikely that Eclipse influences your global settings. If anything outside of Eclipse does not work, should look there for the problem first. Eclipse can either use your system wide settings, or it's own overrides.
I understand your frustration - hard to know what is going wrong.. I really don't see what Eclipse can be doing to cause this though. I can suggest some further troubleshooting steps though.
Can you test the proxy config on any other machine?
Can you browse normally on this machine at other times?
Can you go to the same URL in browser that Eclipse is going to?
Perhaps do you have Eclipse checking all sites for updates (Help > Software) and this is just network slowdown?
When you are experiencing this effect, can you ping outside sites?
I have deployed my GWT application to its target environment (i.e. compiled and copied the war directory contents to the target device's /var/www) and some parts of it are not working. I understand that I can debug my local instance of the GWT app as if it were running in the target environment, by opening the deployed GWT App URL and adding gwt.codesvr URL parameter to it, like this:
http://deployment_host/gwtapp.html?gwt.codesvr=localhost:9997
I get
Plugin failed to connect to Development Mode server at localhost:9997
Follow the underlying troubleshooting instructions
My Chrome browser is running on the same machine as Eclipse, so localhost above should be ok. Just to make sure, I've added -bindAddress 0.0.0.0 in the Run/Debug configuration in Eclipse and tried with my external IP/hostname, with no change, except that the error message is updated accordingly. What am I doing wrong?
If I replace deployment_host with localhost above everything works fine, but it's of no use to me to debug locally. (There is some Proxy and ReverseProxy-ing going on in the local Apache, so I do not need the 8888 port when running locally, but this should be unrelated)
Questions Debugging GWT applications outside of dev mode? and Debug GWT application in a remote browser are related but do not help.
If you are using chrome, look in the address bar at the right for a grey GWT icon. In any other browser, you would see a popup message confirming that you want to debug, but in Chrome this apparently isn't possible.
Click the icon, and it will ask you to whitelist this site as allowed to run Java locally on your computer. After you whitelist it, it should run correctly.
Along the same lines as the answer above Ive just had some success restarting the extension helped (but restarting browser hadnt)
Just enable and disable it in :
chrome://chrome/extensions/
Good luck! It's the only thing wrong with GWT imho...