New answers tagged


Your use-case is the public client as described in RFC 6749 Section 2.1. In this case you have the option to implement the implicit grant. This implies that the user interacts with your site to grant access to the data. However if your use-case forbids the redirection of the user the OAuth framework can't solve your problem.


A VPN masks your IP address. But the HTML5 geolocation API isn't based on your IP address. It is a Javascript API which can be used to ask the web browser directly where it thinks it is located according to whatever information is available to it (system locale settings, nearby wifi networks, GPS sensors, IP address of the network interfaces as you see them ...


Your VPN does not route all traffic through the vpn interface - in particular, the encapsulated vpn traffic itself necessarily travels via your normal internet connection - otherwise it could not reach your other vpn endpoint. This may allow to determine your "official" IP (which would be the external IP of your access router in the typical case of a NATted ...


Try disabling HTML5 geolocation if you don't use it. In Firefox, set geo.enabled to false in about:config. There have been bugs, and there will be again, example 1 and example 2.


I just checked this with my VPN in Although I VPN through Germany, it still shows my nearby location in London. If you read , you will see: If you consent, Firefox gathers information about nearby wireless access points and your computer’s IP address Then Firefox sends this ...

Top 50 recent answers are included