#10027 [Com]: HTTP_REFERER
| From: | XXX-For1635 at hotmail dot com | Date: | Tue, 20 Jul 2004 14:59:03 +0000 |
| Subject: | #10027 [Com]: HTTP_REFERER | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-62730@lists.php.net to get a copy of this message | ||
ID: 10027
Comment by: XXX-For1635 at hotmail dot com
Reported By: brad at youreshop dot com
Status: Closed
Bug Type: *Web Server problem
Operating System: Linux Redhat 6.2
PHP Version: 4.0.4pl1
New Comment:
<a href=http://www.geocities.com/rkhsxefiug2895/>XXX
For</a>
Previous Comments:
------------------------------------------------------------------------
[2003-10-14 14:01:38] paul at bladetechnology dot co dot uk
The last comment was correct. It's caused by one of the Norton products
(Norton Personal Firwall in my case) changing the HTTP_REFERER header
into HTTP_WEFERER (elmer fudd?) and encrypting it. You can solve this
by creating a rule in the firewall software to pass unaltered headers
to named sites.
------------------------------------------------------------------------
[2002-05-09 08:38:17] mn at red1 dot net
I experienced the same problem using PHP4.2.0 (win32) with Apache on
WinME.
On the phpinfo() page HTTP_REFERER was shown as HTTP_WEFERER with a
value of a string of letters.
When I disabled "Norton Internet Security" the problem disappeared.
What is more, scripts on a remote server which were reliant on getting
data from HTTP_REFERER would not run with "NIS" enabled.
Did you have a similar programme running?
------------------------------------------------------------------------
[2002-03-07 06:15:43] sesser@php.net
HTTP_WEFERER has nothing todo with PHP its some
data your browser gives out to the world.
------------------------------------------------------------------------
[2002-03-07 04:19:22] alexleu at starglory dot com
Both windows2000 & FreeBSD 3.4 found SAME Problem With Apache!
How to decode HTTP_WEFERER?
------------------------------------------------------------------------
[2001-04-29 11:50:00] jmoore@php.net
No feedback.
closing
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/10027
--
Edit this bug report at http://bugs.php.net/?id=10027&edit=1