torsdag 19. mai 2011 kl. 16:22:02 UTC+2 skrev cmutter følgende: > > That's a very interesting and helpful insight, thanks! Can > document.referrer then also be manipulated by Internet Security > Software, as some do to outgoing headers? >
No, the http referrer header occurs on the transport layer, which can be altered by proxies, but the document.referrer property only lives within the application and hence you would need e.g. a browser plugin to alter it, that is, if the browser in the first place allows for such an alteration. Sean > On May 13, 3:57 pm, Sean Kinsey <[email protected]> wrote: > > torsdag 12. mai 2011 kl. 22:49:49 UTC+2 skrev gjohnson følgende: > > > > > > > > > As far as I gather the document.referrer property is set via the http > > > header http_referer. I also understand that this header in particular > > > can be blocked from being sent by various proxies and antivirus's like > > > norton. So with that logic in place and assuming it is accurate, why > > > would the http_referer header be stripped out, but document.referrer > > > be populated correctly in some cases? > > > > document.referrer is *not *set based on the referrer header - it's set by > > > the browser based on the url from where the user navigated, just like the > > > referrer header is. > > > > Sean -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
