i have seen some pages that display your current location very accurately and dont seem to be doing it thorough your IP since i tried by using a proxy from another country and they still display my actual location. Is there anyway to get the user location other than by the IP? and if so, is it possible to bypass that so webmasters dont see my actual location?
Thank you.
Read about Geolocation
http://diveintohtml5.info/geolocation.html
Sample page: http://html5demos.com/geo
proxies of this type are supposed to deliver a web experience where that you're location is not shared with anyone but in some cases the actual online proxy- who wouldn't ever use this data. All I can recommend, is a site called hidemyass(dot).com
I found that it tends to use IP address based in the United Kingdom, but that could be based on your own geographical location.
Related
To start this off, let me introduce my problem. I'm currently working on master thesis, which is based on monitoring and blocking HTTP requests that are originated in public internet and destined for devices in local (private) network. These requests could be potentionally malicious, as there's no valid reason for websites in public internet to access local network.
Currently I'm working on the small test webpage, which will demonstrate functionality of my work. For that sake, I'm going to use default router IP address list with combination of given filepaths to manufacturer's logos. So, if you happen to view this webpage, the script in the background basically tries every default IP adress from that list and also will try to access router's manufacturer's logo image. Hopefully one of the requests will hit your router and load up the logo, which will be displayed on the webpage demonstrating this "vulnerability". That page won't be accessible online. It will only come packed with my master thesis at the end of my work.
What I'm asking of you, is to provide me information about your router's manufacturer and as well as a filepath to the image logo (if it happens to have one). So, for example something like this: Asus: /images/New_ui/asustitle.png.
Getting this location should be easy. Just log in to your router, inspect the page and copy&paste src atribute of the <img> (in my case: <img src="images/New_ui/asustitle.png" width="218" height="54" align="left">).
I thank very much to those, who decide to help me with that. I also respect if you don't want to share that information, but believe that my intentions are perfectly sane and valid and it's all just for the purposes of my master thesis.
I'll keep extending the list here:
Asus
/images/New_ui/asustitle.png
TP-Link
/images/top1_1.jpg
For my TP-Link model TL-WR841N the route is /images/top1_1.jpg.
As in normal Google search page, Google returns me results specific to my location. As i am considering/assuming for this, it gets my ip address my request, find uses location for it and returns the results.
I am writing the proxy server for search engines. So from user browser i get requests for some search terms and server returns search results.
I am curious to know, if from Custom Search API can i get the such results based on some IP address i provide or anything like that, so that i can mock the user location in my proxy server and pretend the Google Custom Search to be that user and get the location specific results
PS.I am new to this search engine api world, so please understand me.
Yes, you can, but just for the country, not the exact location.
Here is the docs for parameters of a query request:
https://developers.google.com/custom-search/json-api/v1/reference/cse/list
Look at the 'gl' parameter.
I'm not aware of any way to specify the location more precisely then this.
After these many years I'm not sure if you still need it, but I found it hard to find a helpful answear, so here's the solution for whoever needs it.
You can achieve that behavior with the "?gl=" query param as mentioned here, and pass the value as one of the country codes.
Worked for me, hope it helps someone!
we are developing site (unfortunately on Joomla), where we need to restrict access to some content - articles (and also categories if possible).
Ideally, this content should be hidden even from menu. It will be enough if we were able to specify three access levels for our articles:
public visibility
visible only for intranet
visible only for extranet
Unfortunately we found no extension that could meet our requirements.
Do you have any suggestions, where we should implement this IP filter (detect IP address and check if it is from intranet or extranet is simple task, but we are quite new to Joomla API).
Approach 1 would be a System plugin, as #Lodder suggested. It would pick $_SERVER['REMOTE_ADDR'] (check this, as if you're behind a proxy, another variable might need checking - like X-FORWARDED-FOR or another). Then you can check it vs. conditions set for the article or category — yet to decide how exactly you would mark a particular article as 'Intranet only'. In case of 'access denied' just redirect visitors to the home page. All articles would be open to all by default, and can be market either 'intranet' or 'extranet'.
Approach 2 would be to have two sites instead of one, sharing same database. They can use individual template files, picking different module positions to place menus. Thus there will be two sets of menus in the system: one for Intranet, one for Extranet. Of course in this case anyone with a correct link would be able to access any article, no matter what IP he comes from. So its just a decoration.
i heard about many ways that depend of files like csv or database
but i think uploading an extra database on my site to do that is not good idea
i feel good about the external providers
is useing externial site that give your the country by the ip is good way
or its not good because the server will wait the response of the external provider and this will slow down the site?
Look at this: http://www.rubyquiz.com/quiz139.html
It's actually not a great idea to base the language choice on the IP address anyway. What if I'm an American browsing from Germany, and I don't speak German very well? Your most standards-compliant way (I think) would be to parse the Accept-Language header of the web request, and use that to set a user's default, but always provide them a way to override the default and pick their language (which you'd then store in their session or user prefs)
I would use PHP variable $_SERVER['HTTP_ACCEPT_LANGUAGE'] which, in my case, holds this value sk,cs;q=0.8,en-us;q=0.5,en;q=0.3. That means, my browsers language is 'Slovak'.
I think, this option is better. Just imagine, that you are English, but you are on vacation somewhere.You use your notebook over there... Your IP address would tell your server, that you are in Croatia and you'd like to get content in their language... But you browser still says you are english speaking person... There is the difference ;)
I wouldn't use GeoIP for this - there are too many scenarios when it fails or produces the wrong results.
As #Paul says the HTTP Accept-Language header specifies the user's language preferences as defined in the browser. You can view what your browser is set to by visiting Browser Language Detection.
For a real worked example see Parse Accept-Language to detect a user's language.
Also remember that crawlers don't use Accept-Language so it is important to ensure that you have a strategy for making this available (e.g URLs for each language content) and include in sitemap.
Also see Apache Module mod_negotiation for content selection.
Does anyone know how to setup Google Analytics to filter yourself out if you're visiting the site from a dynamic IP address? I don't want to include myself in my stats from home use where I have a dynamic IP address via Verizon FiOS.
Google currently has a browser add-on that will block any visits of yours from showing up in any Analytics. http://tools.google.com/dlpage/gaoptout
Pluses and minuses of this opt-out versus filters are discussed in this blog post.
There are a couple ways of doing this. If you know the range of IP addresses you're accessing your site from (and don't mind filtering them all out) you can set up an "Exclude" filter for that range of IP addresses. If that's too restrictive, you can set a cookie using the Google Analytics code and filter on that. Both techniques are documented at Google's help system.
Alternatively, if you're dynamically producing the pages on the server, you could simply not write the Google Analytics code into the pages in the first place, based on the currently logged in user. On my site, I'm choosing to write the code or not based on a few things, such as whether the website is running in debug mode or if an administrator is logged on.
You can do this by creating a special page on your site that sets a Google Analytics segmentation cookie, using code something like:
<body onLoad="javascript:__utmSetVar('exclude_from_report')">
Then create a custom filter in Analytics to exclude visitors that match the 'exclude_from_report' segment pattern.
Consider using the NoScript plugin for Firefox. Just mark google-analytics.com as an untrusted site and you should be all set. A nice side-benefit: better security in your browser.
Just block the domain where google analytics lives via your system's hosts file:
127.0.0.1 www.google-analytics.com
This is less disruptive than the NoScript plugin mentioned by jdigital, but still makes you effectively invisible to google analytics.
Setting a cookie to prevent the analytics code from being sent to the browser is by far the best option.
If you're a developer and concerned that you're going to get a bazillion hits while you're developing the site you can add the following line in your analytics tracking code :
pageTracker._setDomainName(".yourwebsitename.com");
Assuming you're hitting a url not ending in .yourwebsitename.com during testing then the tracking code will see your URL is 'localhost' and not 'yourwebsitename.com' and not send any tracking.
You can always setup a proxy to tunnel all of your traffic through. Then simply exclude the proxy's IP from the results.
can't find a way to reply to answers, I second to the hosts file trick:
127.0.0.1 www.google-analytics.com
as it works in all browsers at the same time, as designers often try site in all browsers.
I recommend to use a 127.0.0.1 (localhost) redirect in the HOST file to block all/any type of abusive sites or domain/trackers/analytic and such. For a large list take a look at the WinHelp website. I have and still use it for all my PC's. You also need to look over the list which domains you do want and remark the lines with a # tag in the list.
All instructions are on the site for different operating systems.