-
Notifications
You must be signed in to change notification settings - Fork 3.9k
nw requests to google servers #4669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Anyone knows the content of these requests? Usage details, visited sites? |
This requests are sends via https to 443 port. |
@VoidVolker could you please turn log on and set command line argument '--v=1' so it might show what it is doing? See https://www.chromium.org/for-testers/enable-logging on how to enable logging. And please make sure to clear the user data directory of 'nwjs' app first. |
GCM is disable now by default. So the requests may not be for GCM. |
I need use this command as |
As I said previously, it's a command line argument. |
Not reproducing :( Can't catch again - it happens in some random times... |
I guess removing user data dir would help. |
Yes! Thanks - this helps. Logic is next:
In this case here was 2 attempts:
|
Have you got the log? |
Here the log:
Ip lists - in this time there was 4 attempts:
|
Your log is very incomplete, it should looks like: ''' |
This all, what I have in log. |
I have to get the full log to know what's happening there. Did you follow the instructions in https://www.chromium.org/for-testers/enable-logging ? |
Yes. You can see in log:
|
It's obviously not the full log. So something wrong is obviously happening in either your steps of acquiring log, or a bug in NW logging code. |
What else I can do? My actions:
|
Where did you get the log? |
In same dir with nw.exe, file is |
If you read the link carefully, you would know it should be 'chrome_debug.log' in the user data directory. And you need to use both '--enable-logging' and '--v=1'. |
Ah... Ok. Here the log - but there nothing information about this requests, if requests is blocked. But, if allow connections:
|
This is fixed in git and will be available in the next nightly build. |
Cool! Thanks, Roger. |
No more this strange requests. What was this? Requesting plugins list? I'm cheked file http://www.gstatic.com/chrome/config/plugins_2/plugins_win.json - there plugins list, links and mime types. |
It's plugin metadata used for showing 'chrome://plugins'. The request is sent to update the local metadata which is builtin in the On Mon, Apr 4, 2016 at 12:38 AM VoidVolker [email protected] wrote:
|
nwjs 0.13.x
Known IPs:
https://groups.google.com/d/msg/nwjs-general/HF7InrhFxqw/FxQGrIcGCAAJ
https://developer.chrome.com/apps/gcm
The text was updated successfully, but these errors were encountered: