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
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
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
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
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
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
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
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
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
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
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
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
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
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
@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
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
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
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
--
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
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.
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...
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
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
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
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
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
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
27 matches
Mail list logo
