Also from Section 14.36 of rfc2616:
extract
The Referer field MUST NOT be sent if the Request-URI was obtained from
source that does not have its own URI, such as input from the user keyboard.
/extract
So you can't rely on it being present.
Shapira, Yoav wrote:
Hi,
But I have 2 questions:
1.
Ok, I misunderstood what it did. It seems to work ok on both IE and
Firefox always returning a value when navigating from a page but being
null when accessing the page directly because there is no referer.
So Ive just coded my page like to only show a back link when actually
come from another
I have a WebPage which can be called from two different webpages, and I
wanted it to have a back button.
Originally I had the calling pages passing a parameter to tell the
called page what called it. Then someone pointed
out %=request.getHeader(REFERER)% to m. This works much better.
But I
Hi,
But I have 2 questions:
1. Where are these header values defined I've not beeen able to find a
good source.
See the HTTP protocol RFC itself for common headers like referrer.
Other servers and routers may add custom headers along the way. Your
app and other apps can also use custom headers
The browser generates the HTTP headers and there are some rules
governing when they are to be sent.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
This isn't really Tomcat specific so I'm marking [OT]
You may find more enthusiastic help on a JSP/Servlet list.
-Ben
On Wed,
On Wed, 2004-11-10 at 12:52, Ben Souther wrote:
The browser generates the HTTP headers and there are some rules
governing when they are to be sent.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
This isn't really Tomcat specific so I'm marking [OT]
You may find more enthusiastic