<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1003328" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1003328</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/php-and-error-documents#comment-1014629</link>
    <description> &lt;p&gt;That is strange... I didn&#039;t even think about it being refrenenced like that. I am not an Apache guru so don&#039;t look at me for an answer, though I will see what I can find as it is curious.&lt;/p&gt;
&lt;p&gt;Glad you got it working though.&lt;/p&gt;
&lt;p&gt;------------------&lt;br /&gt;
&lt;strong&gt;Dynamic Internet Solutions :  &lt;a href=&quot;http://www.dids.com&quot; class=&quot;bb-url&quot;&gt;http://www.dids.com&lt;/a&gt;&lt;br /&gt;
Windows NT and UNIX Hosting&lt;/strong&gt;&lt;/p&gt;
 </description>
     <pubDate>Sun, 13 Feb 2000 01:54:00 +0000</pubDate>
 <dc:creator />
 <guid isPermaLink="false">comment 1014629 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/php-and-error-documents#comment-1014628</link>
    <description> &lt;p&gt;Hmmm, okay, let&#039;s chalk this one up as &quot;you learn something new and strange every day&quot;.&lt;/p&gt;
&lt;p&gt;I tried your suggested code and it did the same thing as mine, just returning 404.php3 instead of the requested file name. However, the fact that it worked for you and not for me led me to delve deeper into the problem. I played around with a few things and found the real culprit. I had that one error document in my .htaccess file referenced as a full domain name (&lt;a href=&quot;http://www.whatever.com/404.php3&quot; title=&quot;http://www.whatever.com/404.php3&quot;&gt;http://www.whatever.com/404.php3&lt;/a&gt;) instead of just a relative path of /404.php3.  That, for whatever reason, was causing the $REQUEST_URI to be rewritten. I guess the way it accessed that file was adding an extra step into the equation and that step was the one that was getting logged. Or, if I&#039;m wrong about that, maybe one of you Apache gurus can tell me what really happened.&lt;/p&gt;
&lt;p&gt;Anyway, for&lt;br /&gt;
ErrorDocument 404 /404.php3&lt;/p&gt;
&lt;p&gt;both &amp;lt;? print $REQUEST_URI ?&amp;gt; and &amp;lt;?php echo getenv(REQUEST_URI); ?&amp;gt; work fine&lt;/p&gt;
&lt;p&gt;for&lt;br /&gt;
ErrorDocument 404 &lt;a href=&quot;http://www.domain.com/404.php3&quot; class=&quot;bb-url&quot;&gt;http://www.domain.com/404.php3&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;neither code works. Thanks for the help Chad.&lt;/p&gt;
 </description>
     <pubDate>Sat, 12 Feb 2000 21:46:00 +0000</pubDate>
 <dc:creator>Maverick</dc:creator>
 <guid isPermaLink="false">comment 1014628 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/php-and-error-documents#comment-1014627</link>
    <description> &lt;p&gt;Maverick,&lt;/p&gt;
&lt;p&gt;Try using this&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;code:&lt;/p&gt;
&lt;pre&gt;&amp;lt;?php echo getenv(REQUEST_URI); ?&amp;gt;[/code]

Instead of this:

&lt;BLOCKQUOTE&gt;code:&lt;pre&gt;&amp;lt;? print $REQUEST_URI ?&amp;gt;[/code]


That is what we use on our error pages that do what you would like (except the error e-mail is automatically e-mailed to us which is more effective than having a visitor push the &quot;Notify&quot; button). It should work.

------------------
&lt;strong&gt;Dynamic Internet Solutions :  &lt;a href=&quot;http://www.dids.com&quot; class=&quot;bb-url&quot;&gt;http://www.dids.com&lt;/a&gt; 
Windows NT and UNIX Hosting&lt;/strong&gt; &lt;/pre&gt;&lt;/blockquote&gt;&lt;/pre&gt;&lt;/blockquote&gt;</description>
     <pubDate>Sat, 12 Feb 2000 20:45:00 +0000</pubDate>
 <dc:creator />
 <guid isPermaLink="false">comment 1014627 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
