>From client's perspective, navigator check doesn't care nor sees proxies. It >tries to do a connection and that's it.
Alternatively look at what you've got. Internet-available makes a dns query, but your proxy/firewall does not allow direct communication. But a simple http fetch should work, if your app uses default system proxy configuration (in vast majority of the cases). So I would guess that a combo of no-direct-dns (or anything outgoing, for that matter), but normal connection from the client-side script which uses something like automatic (OS-controlled) proxy config should tell you it is a proxy. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/a61f88b7-8308-43f7-9590-cd82adb2008d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
