Search Results

Search found 2 results on 1 pages for 'joshuahedlund'.

Page 1/1 | 1 

  • Difference between two kinds of Bing URL Referers

    - by joshuahedlund
    Most of the referral URLS that I get from Bing have the following syntax: http://www.bing.com/search?q=keywords+keywords&[some other variables] However I just noticed that maybe 10-20% of them are coming in like this: http://www.bing.com/url?source=search&[some other variables]&url=http%3A%2F%2Fwww.example.com/user-landing-page-on-my-site&yrktarget=_top&q=keywords+keywords&[some other variables] The first syntax gives me the keywords the user typed in, but the second actually gives me the keywords the user typed in and their landing page on my site. I was originally unaware of this second kind altogether because I have a customized referral report that filters out URLs containing my domain. But now that I noticed them I want to know why they occur to see if I can get more to occur this way because the second syntax contains more valuable information. If I go to one of the first URLs, it gives me a typical Bing query page. The second URLs seem to just redirect me to the Bing home page. I'm not sure if it has to do with the kind of search being performed (I also get a few http://www.bing.com/shopping/search?q= referers) or some other metric. Does anyone know what causes some referral URLs from Bing to have the /search?q syntax and others to have the /url?source syntax? P.S. I have verified that I am getting both kinds of URLs from non-advertising clicks. P.P.S. I am not talking about data in Google Analytics or similar software but the raw $_SERVER['HTTP_REFERER'] value coming from the client's original request.

    Read the article

  • Is there any problem with using two slashes in the middle of a URL? [closed]

    - by joshuahedlund
    Possible Duplicate: What does the double slash mean in URLs? I'm working on a mod_rewrite URL structure as follows: http://example.com/search/filter1/filter2/filter3/filter4 There are some conditions where it is OK for the first attribute to be blank, but i want to keep the other attributes in the same position. (Otherwise I can't assume that the attribute in the second position represents what I want it to represent.) However this results in some URLs like this: http://example.com/search//filter2/filter3/filter4 This seems to work in all browsers I've tested (Chrome,Firefox,IE9,IE compatible) and I'm not seeing any errors on the server side, so I can't think of any problems in using it. But it just looks wrong and weird to me and I'm not used to seeing it. Are there any potential downsides to using a structure that encourages URLs like this, or any major reasons no one seems to use it? (Everything I search in Google assumes I'm talking about the two slashes after http:)

    Read the article

1