Re: [WSG] Where did I come from?
Hi Martin and others, On 19/1/08 1:45 AM, Martin Heiden wrote: 2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user You can access it via (PHP|Java|ASP|...) or by JS document.referrer Just out of interest, what happens when HTTP-Header Referrer is suppressed? Does the page remain unchanged, is there a 404, or some other error? -- Sarah Peeke XERT Communications Email: [EMAIL PROTECTED] Skype: s.peeke Website: http://xert.com.au/ LinkedIn: http://www.linkedin.com/in/sarahpeeke Geofeat International: http://geofeat.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Sarah Peeke wrote: Hi Martin and others, On 19/1/08 1:45 AM, Martin Heiden wrote: 2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user You can access it via (PHP|Java|ASP|...) or by JS document.referrer Just out of interest, what happens when HTTP-Header Referrer is suppressed? Does the page remain unchanged, is there a 404, or some other error? Sarah, Referer is just one HTTP header - it is separate from response codes (200, 404 etc) and other headers. No error is thrown if it's not present so content is passed on as normal. But because HTTP headers can be changed along the response chain from server to client they can't be relied upon. -- Chris Knowles *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Chris Knowles wrote: Sarah Peeke wrote: Hi Martin and others, On 19/1/08 1:45 AM, Martin Heiden wrote: 2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user You can access it via (PHP|Java|ASP|...) or by JS document.referrer Just out of interest, what happens when HTTP-Header Referrer is suppressed? Does the page remain unchanged, is there a 404, or some other error? Sarah, Referer is just one HTTP header - it is separate from response codes (200, 404 etc) and other headers. No error is thrown if it's not present so content is passed on as normal. But because HTTP headers can be changed along the response chain from server to client they can't be relied upon. actually, I should have said changed along the request/response chain between server and client. -- Chris Knowles *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On 22/1/08 1:37 PM, Chris Knowles wrote: Referer is just one HTTP header - it is separate from response codes (200, 404 etc) and other headers. No error is thrown if it's not present so content is passed on as normal. But because HTTP headers can be changed along the response chain from server to client they can't be relied upon. Hi Chris, Thanks for your reply. So, if the HTTP headers are changed along the response chain from server to client what is the likely outcome? Where would the user be directed in this case? Cheers, -- Sarah Peeke XERT Communications Email: [EMAIL PROTECTED] Skype: s.peeke Website: http://xert.com.au/ LinkedIn: http://www.linkedin.com/in/sarahpeeke Geofeat International: http://geofeat.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On Jan 22, 2008 3:58 PM, Sarah Peeke [EMAIL PROTECTED] wrote: So, if the HTTP headers are changed along the response chain from server to client what is the likely outcome? Where would the user be directed in this case? That depends on the application. It's not a required field, but that doesn't mean that applications shouldn't make decisions based on it. A good example of web software that makes decisions based on referrers are anti-image-leech scripts*. -- .Matthew Cruickshank http://holloway.co.nz/ [*] and image leech scripts are a good response to kids that use your photos http://holloway.co.nz/returnoftheking/ and drain through gigs of traffic... because then you start serving up something like this instead http://holloway.co.nz/image-leech.jpg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On Tue, 22 Jan 2008 13:58:52 +1100, Sarah Peeke wrote: So, if the HTTP headers are changed along the response chain from server to client what is the likely outcome? Where would the user be directed in this case? HTML doesn't care. Its possible to write server-side code that generates different markup based on the referer, or even js code the same, but HTML on its own doesn't read the referer to care what it says or doesn't say and will display the same. warmly, Lea -- Lea de Groot Elysian Systems Brisbane, Australia *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
changed along the response chain from server to client they can't be relied upon. Other way 'round. Referer is a Request header, (optionally) originated by the client. But even user agents that provide one may have it stripped from the Request by personal fire walls, proxies, etc. But since it's optional, servers (and well-written web applications) shouldn't care. :-) http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html#sec5.3 -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-621-3445 === http://webtuitive.com dream. code. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Sarah Peeke wrote: So, if the HTTP headers are changed along the response chain from server to client what is the likely outcome? Where would the user be directed in this case? The user is not directed anywhere, it's just that - in the case we're discussing - the receiving page can't determine the referrer (it's either blank, or changed to something random). As it's not uncommon for headers like http-referer to be rewritten (for instance, anybody using Norton Internet Security has this), it simply means you as a developer can't rely on them (to gather stats on referrers, or create a magical and redundant back button/link, etc). P -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Thanks Pat! On Jan 18 2008, at 17:57, Patrick H. Lauke wrote: Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. They could want to get the referrer for something else. From the thread starter .I just want to know what the previous page was...so I can create a button to go back to it.. P -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ __ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joe Ortenzi [EMAIL PROTECTED] www.joiz.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Thanks David, Glad to see I'm not the only one who read the email carefully before replying. :-) My understanding of web standards is that one does not replace/ duplicate what is part of the standard furniture without a GOOD reason. Replicating functionality that already exists goes against WS does it not? In the same way you do not create a difficult navigation system hat you then have to explain is a navigation system you should not replicate common functionality with a new, space-hogging function. Joe On Jan 18 2008, at 22:38, David Dorward wrote: On 18 Jan 2008, at 17:23, Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. As assumptions go, when they say so I can create a button to go back to it..., it is a pretty safe one. And, not everyone knows about the back button. Don't assume... The back button should be one of the very first things people learn about when they are introduced to the web. If you suspect that your users do not, then creating a custom control that works only for your site instead of educating them about the software they use, is doing them a disservice. Additionally, an in page control marked back causes confusion since users don't know if it will act in the same way as their back button or go forward to the previous URL (which it is will alter the effect on the normal back button). -- David Dorward http://dorward.me.uk/ http://blog.dorward.me.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joe Ortenzi [EMAIL PROTECTED] www.joiz.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
You'd be surprised (maybe not!) as to how few people know about tab and new windows and use them for this purpose. I really have to push people in our studio to use these. Joe On Jan 19 2008, at 12:11, George S. Williams wrote: On Sat, 2008-01-19 at 04:38, Designer wrote: I use this kind of thing all the time - It's called a tab :-) I use that thing quite a bit also. And, occasionally, a similar thing called a new window... George *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joe Ortenzi [EMAIL PROTECTED] www.joiz.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Martin Heiden wrote: Simon, on Friday, January 18, 2008 at 15:24 wsg@webstandardsgroup.org wrote: I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... You can't! There are some properties that hold the value you are looking for, but these aren't reliable: 1. javascript:history.back() - only works if JS is turned on. 2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user You can access it via (PHP|Java|ASP|...) or by JS document.referrer Any ideas on how easy it would be for a user to dissable such a feature of their firewall software, I'm guessing it would be a hidden feature usually. Garrr, unnecessary protection that will cause more problems to outweigh the protection it offers IMHO. regards Martin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Christian Snodgrass wrote: When I read that, I thought about creating a button that finds the site you were at before you came in here, and then keeps that the same throughout the site, so no matter how many pages you go to, you can get back out of all of those and back where you were before you started that. That's a bit different functionality then a standard back button on an internet browser. I use this kind of thing all the time - It's called a tab :-) Bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On Sat, 2008-01-19 at 04:38, Designer wrote: I use this kind of thing all the time - It's called a tab :-) I use that thing quite a bit also. And, occasionally, a similar thing called a new window... George *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Where did I come from?
If the back button doesn't work, then I think you will find that history.go won't work either. Mike From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Ten Sent: Friday, January 18, 2008 2:41 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Where did I come from? You can use history.go(-1) to go back. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
You can use history.go(-1) to go back. Also, there is document.referrer string, but it could be empty. On Jan 18, 2008 5:24 PM, Simon Cockayne [EMAIL PROTECTED] wrote: Hi, I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... Cheers, Simon *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Алексей *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
But why? everyone knows about the back button, don't they? So you don't really need to help them. And if the previous site was yours and you want to see if they went from your site A to your site B then you could probably do this with sessions or by passing a variable forward through the link using a server-side language like ASP or PHP. If all you want to do is allow them to go back to where they were before they came to you, tell them about the back button in their browser. One option is to set up Google Analytics on the site, so you can see the referrers without any messy coding, otherwise, it's really none of your business is it? You could create a function on all of your pages that, if they have never been there before and don't have your cookie, to ask them where they came from and show them their back button, but really, it isn't any of your business. So I suppose the web Standards part of this question is about polite behaviour? Joe On Jan 18, 2008, at 14:24, Simon Cockayne wrote: Hi, I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... Cheers, Simon *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** == Joe Ortenzi [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. They could want to get the referrer for something else. From the thread starter .I just want to know what the previous page was...so I can create a button to go back to it.. P -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ __ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On 18 Jan 2008, at 14:24, Simon Cockayne wrote: I am on a webpage...how do I know what page the browser was previously showing. Reliably? You can't. Unreliably? The (optional) HTTP referer header (which is munged by some personal firewall solutions). NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... The user already has several of those. -- David Dorward http://dorward.me.uk/ http://blog.dorward.me.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
On 18 Jan 2008, at 17:23, Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. As assumptions go, when they say so I can create a button to go back to it..., it is a pretty safe one. And, not everyone knows about the back button. Don't assume... The back button should be one of the very first things people learn about when they are introduced to the web. If you suspect that your users do not, then creating a custom control that works only for your site instead of educating them about the software they use, is doing them a disservice. Additionally, an in page control marked back causes confusion since users don't know if it will act in the same way as their back button or go forward to the previous URL (which it is will alter the effect on the normal back button). -- David Dorward http://dorward.me.uk/ http://blog.dorward.me.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
I completely agree with most of the comments so far. Why create functionality that is simply replicating the functionality of a browser? There was an article on text resizing a while ago that I'm sure most people are already aware of by Roger Johansson... http://www.456bereastreet.com/archive/200709/scrap_text_resize_widgets_and_teach_people_how_to_resize_text/ I'd consider text resizing quite advanced compared to using the back button so I personally think that trying to recreate this kind of functionality is actually a step backwards in trying to educate our users. - - - - - - - - - - http://www.dave-woods.co.uk On 18/01/2008, David Dorward [EMAIL PROTECTED] wrote: On 18 Jan 2008, at 17:23, Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. As assumptions go, when they say so I can create a button to go back to it..., it is a pretty safe one. And, not everyone knows about the back button. Don't assume... The back button should be one of the very first things people learn about when they are introduced to the web. If you suspect that your users do not, then creating a custom control that works only for your site instead of educating them about the software they use, is doing them a disservice. Additionally, an in page control marked back causes confusion since users don't know if it will act in the same way as their back button or go forward to the previous URL (which it is will alter the effect on the normal back button). -- David Dorward http://dorward.me.uk/ http://blog.dorward.me.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
When I read that, I thought about creating a button that finds the site you were at before you came in here, and then keeps that the same throughout the site, so no matter how many pages you go to, you can get back out of all of those and back where you were before you started that. That's a bit different functionality then a standard back button on an internet browser. And I got that idea from the other thread that the thread starter made about an internal application that refuses to let you leave the site. Patrick H. Lauke wrote: Christian Snodgrass wrote: You shouldn't always assume that they are just trying to replace the back button. They could want to get the referrer for something else. From the thread starter .I just want to know what the previous page was...so I can create a button to go back to it.. P -- Christian Snodgrass Azure Ronin Web Design http://www.arwebdesign.net/ http://www.arwebdesign.net Phone: 859.816.7955 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
Simon, on Friday, January 18, 2008 at 15:24 wsg@webstandardsgroup.org wrote: I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... You can't! There are some properties that hold the value you are looking for, but these aren't reliable: 1. javascript:history.back() - only works if JS is turned on. 2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user You can access it via (PHP|Java|ASP|...) or by JS document.referrer regards Martin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Where did I come from?
Hi, I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... Cheers, Simon *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
You shouldn't always assume that they are just trying to replace the back button. They could want to get the referrer for something else. And, not everyone knows about the back button. Don't assume... Joseph Ortenzi wrote: But why? everyone knows about the back button, don't they? So you don't really need to help them. And if the previous site was yours and you want to see if they went from your site A to your site B then you could probably do this with sessions or by passing a variable forward through the link using a server-side language like ASP or PHP. If all you want to do is allow them to go back to where they were before they came to you, tell them about the back button in their browser. One option is to set up Google Analytics on the site, so you can see the referrers without any messy coding, otherwise, it's really none of your business is it? You could create a function on all of your pages that, if they have never been there before and don't have your cookie, to ask them where they came from and show them their back button, but really, it isn't any of your business. So I suppose the web Standards part of this question is about polite behaviour? Joe On Jan 18, 2008, at 14:24, Simon Cockayne wrote: Hi, I am on a webpage...how do I know what page the browser was previously showing. I think Javascript History object is the ticket...but STRICT mode in Firefox seems to tell me that I don't have permission to access it. NOTE: I don't want to use the History object to go back or forward...I just want to know what the previous page was...so I can create a button to go back to it... Cheers, Simon *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** == Joe Ortenzi [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Christian Snodgrass Azure Ronin Web Design http://www.arwebdesign.net/ http://www.arwebdesign.net Phone: 859.816.7955 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Where did I come from?
are there any SSI whizzes out there? I would have thought that you could use the referrer in an SSI to accomplish this sort of functionality. BTW: I am astonished at how few people understand the back button. And many more who don't trust it: a result of abuse, no doubt, from sites that break the behaviour or use unnecessary 'post' values that cause 'resubmit' problems. That being said, I think a back button is a bad idea as it only ingrains this behaviour... users end up believing if there is no button, they can't get back. -- Andrew Harris [EMAIL PROTECTED] http://www.woowoowoo.com ~~~ * ~~~ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Where did I come from?
When I read that, I thought about creating a button that finds the site you were at before you came in here, and then keeps that the same throughout the site, so no matter how many pages you go to, you can get back out of all of those and back where you were before you started that. That's a bit different functionality then a standard back button on an internet browser. They could want to get the referrer for something else. Sounds more like that to me ... actually it sounds to me more like they want the referrer received at the first page where they entered the site to be shown as a link on all pages viewed after that. I guess you would then need to store that first referrer somewhere, perhaps in a user session if you are using a session manager. (such as php's $_SESSION, etc) I don't really understand why they could assume that a page they came from (first referrer) is *always* the page they are likely to want to go back to. That page could be anything with a link to that site on it, possibly search results, etc *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
