I’d do it like this $referringPage = parse_url( $_SERVER[‘HTTP_REFERER’] ); if ( stristr( $referringPage[‘host’], ‘google.’ ) ) { parse_str( $referringPage[‘query’], $queryVars ); echo $queryVars[‘q’]; // This is the search term used }
this function should give you a starting point it will fetch any http url with the specified referrer handling the query parms should be pretty trivial, so i will leave that part for you to do <?php echo geturl(‘http://some-url’, ‘http://referring-url’); function geturl($url, $referer) { $headers[] = ‘Accept: image/gif, image/x-bitmap, image/jpeg, image/pjpeg,text/html,application/xhtml+xml’; $headers[] = ‘Connection: Keep-Alive’; … Read more
HTTP_REFERER is not guaranteed to be sent by the client: The address of the page (if any) which referred the user agent to the current page. This is set by the user agent. Not all user agents will set this, and some provide the ability to modify HTTP_REFERER as a feature. In short, it cannot … Read more
Store it either in a cookie (if it’s acceptable for your situation), or in a session variable. session_start(); if ( !isset( $_SESSION[“origURL”] ) ) $_SESSION[“origURL”] = $_SERVER[“HTTP_REFERER”];
Set the referer using – setValue:forHTTPHeaderField: NSMutableURLRequest* request = …; [request setValue:@”https://myapp.com” forHTTPHeaderField: @”Referer”]; But note that according to the HTTP RFC you shouldn’t, because your app is not addressable using a URI: The Referer field MUST NOT be sent if the Request-URI was obtained from a source that does not have its own URI, … Read more
As a general rule, you should not trust the HTTP Referer Header for any matter of importance, except for purely informative statistical analysis of who your visitors are or when looking for patterns of behaviour among the users of your own site. Under no circumstance it is advisable that you use this header for AAA … Read more
I don’t know about the 302, but I tested the 301 on some browsers today, here the results: SCENARIO: user clicks link on domainX that points to domainA. domainA does a 301 redirect to domainB. IE8 referer when landing on domainB is: domainX (even when using InPrivate browsing and even when user opens link in … Read more
You could use the UrlReferrer property of the current request: Request.UrlReferrer This will read the Referer HTTP header from the request which may or may not be supplied by the client (user agent).
It will/may be empty when the enduser entered the site URL in browser address bar itself. visited the site by a browser-maintained bookmark. visited the site as first page in the window/tab. clicked a link in an external application. switched from a https URL to a http URL. switched from a https URL to a … Read more
The REFERER is sent by the client’s browser as part of the HTTP protocol, and is therefore unreliable indeed. It might not be there, it might be forged, you just can’t trust it if it’s for security reasons. If you want to verify if a request is coming from your site, well you can’t, but … Read more