S�ren, When I created a 404.taf to handle moved pages (i.e. we restructured the site and 404.taf handles the "This page has moved" code), I found that the information about the original URL that had been entered was stored in the <@CGIPARAM "HTTP_SEARCH_ARGS"> tag. This isn't where I expected to find it.
That was on IIS/5. So, on Apache, it may be stored in some other unexpected parameter. I guess you need to spew out all the possibilities until you find how Apache behaves. Jon -----Original Message----- From: S�ren Christian Rix [mailto:scrix@;unlimited.dk] Sent: 27 October 2002 12:44 To: Multiple recipients of list witango-talk Subject: Witango-Talk: 404 redirect with Apache and Witango5 on Win2000 Hi, I'm trying to do something clever with 404 errors on Apache/win2000. I've entered the line: ErrorDocument 404 /404.taf in the virtual host of the domain I'm working with in httpd.conf and created a 404.taf. the result of this is that the 404.taf gets shown when I hit a non-existing url. The problem is that I can't access the important @CGIPARAM's like REFERER or HTTP_SEARCH_ARGS. How do I do that? -at least I need to retrieve the original full request to show an intelligent error message or do a relevant redirect. Thanks for your time S�ren Christian Rix ---------------------------------------------- - S�ren Christian Rix [EMAIL PROTECTED] - - Unlimited Aps tlf +45 97123300 - - R�nneb�rvej 8 fax +45 97123365 - - DK-7400 Herning gsm +45 20734220 - - Denmark priv +45 97214220 - ---------------------------------------------- ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
