Last post Jul 09, 2005 08:11 AM by ariya
May 18, 2005 12:58 PM|JNatUK|LINK
What does it mean when
context.Request.UrlReferrer is sometimes null?
May 18, 2005 03:58 PM|wswartzendruber|LINK
May 21, 2005 11:22 AM|master4eva|LINK
Well... start up your browser and type in the address. You will see that the URL referrer is null/nothing because nothing referred the browser to the page. Put that in a context that someone sent someone else an email with a direct link - the referrer is
not a web page so that won't be transmitted to the server. Essentially, those normal activities will entail your 50% of null referrers.
The other 50% can be caused from internet security suites. Basically, what the dudes did is removed IE's transmission of the referrer page because some people see it as an evasion of privacy to see whom came from where. With Norton, I think they do still
transmit the referrer by the "WRL_REFFERRER" HTTP header but the UrlReferrer property looks at the HTTP transmission of URL_REFFERRER. (I know the spelling is wrong... so did the standards mispell it as well and my brain is so confused now).
It's a big picture to put together but I hope you can start getting some ideas what is happening.
Jun 28, 2005 05:43 PM|jkunkle|LINK
Jul 09, 2005 08:11 AM|ariya|LINK