[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Passing HTTP_REFERER to a custom 404 page?
- Subject: RE: [cobalt-users] Passing HTTP_REFERER to a custom 404 page?
- From: "Clark E. Morgan" <prlhkr@xxxxxxxxxxxxx>
- Date: Tue May 8 21:54:09 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> Thanks - but the servervariables collection is precisely what I've been
> trying to use. Most of the variables are there, but http-referer' (and
> variations on the theme) are blank. I believe this may be a configuration
> setting of some sort, but I am at a loss to know what.
Hmmm, it may be that this technically is not a referer situation (although
you might want to make sure that you didn't inadvertently use a 'rr' where
its only supposed to be 'r' - I've made this mistake to my considerable
consternation any number of times.
I'd also try doing a tail -f on my referrer log while deliberately
requesting
a bad page in another window and see if it actually gets passed. If not, it
may
be that Apache has to pass it for asp to recognize it, which is as simple as
uncommenting the appropriate line in httpd.conf. Of course, if it's not set
up then you'd have no referer_log aat all. Otherwise, it simply may not
count
as a referring url. In php, I can simply call SCRIPT_NAME and the
non-existent
script is what gets passed, not the actual 404 page. Perhaps the asp
equivalent
is what you would use.
Failing that. you could try instead relying on javascript with its
history(-1).
Not sure if you'd want to pass that back.
I'll be interested to know what you eventually find out. Good Luck.
Clark Morgan