403 question

I have used the "ErrorDocument 403" directive in my httpd.conf file
(of Apache 1.3.27) to point to a dynamci, JSP file. I would like to
be able to say in that file, "You are forbidden access to
/path_you_accessed/page." Is there a setting in Apache to allow you
to retain the headers from the request that caused the 403, thus
allowing the 403 page to know what caused/called it?

Thanks - Dave

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <9fe1f2ad.0307021240.4a2d8cca@posting.google.com >, D. Alvarado wrote:
> I have used the "ErrorDocument 403" directive in my httpd.conf file
> (of Apache 1.3.27) to point to a dynamci, JSP file. I would like to
> be able to say in that file, "You are forbidden access to
> /path_you_accessed/page." Is there a setting in Apache to allow you
> to retain the headers from the request that caused the 403, thus
> allowing the 403 page to know what caused/called it?

Read the documentation for the ErrorDocument directive, in
particular the docs about custom responses and the environment
variables Apache sets.

- --keith

- --
kkeller-mmmspam@wombat.san-francisco.ca.us
(try just my userid to email me)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj8DSUYACgkQhVcNCxZ5ID/GxQCeKXPpCsZifqOOcxQmshG+kYcS
jZcAniryLPBRYD/fjmp6JDbr7o8xEJzA
=MQqn
-----END PGP SIGNATURE-----

On Wed, 2 Jul 2003, Andreas Paasch wrote:
> Keith Keller wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1

Please don't add that crap to posts. People really don't care if it's you.
Reserve it for your e-mail.

> > In article <9fe1f2ad.0307021240.4a2d8cca@posting.google.com >, D. Alvarado
> > wrote:
> >> I have used the "ErrorDocument 403" directive in my httpd.conf file
> >> (of Apache 1.3.27) to point to a dynamci, JSP file. I would like to
> >> be able to say in that file, "You are forbidden access to
> >> /path_you_accessed/page." Is there a setting in Apache to allow you
> >> to retain the headers from the request that caused the 403, thus
> >> allowing the 403 page to know what caused/called it?
> >
> > Read the documentation for the ErrorDocument directive, in
> > particular the docs about custom responses and the environment
> > variables Apache sets.
>
> Your solution is to find the server generated variables and use them, these
> are easily imbedded in any HTML page.
>
> Using SSI code, these are - briefly:
>
> Document Name: <!--#echo var="document_name" --><br>
> Document URI: <!--#echo var="document_uri" --><br>
> Local Date: <!--#echo var="date_local" --><br>
> GMT Date: <!--#echo var="date_gmt" --><br>
> Last Modified: <!--#echo var="last_modified" --><br>
> Server Software: <!--#echo var="server_software" --><br>
> Server Name: <!--#echo var="server_name" --><br>
> Server Protocol: <!--#echo var="server_protocol" --><br>
> Server Port: <!--#echo var="server_port" --><br>
> Gateway Interface: <!--#echo var="gateway_interface" --><br>
> Request Method: <!--#echo var="request_method" --><br>
> Script Name: <!--#echo var="script_name" --><br>
> Remote Host: <!--#echo var="remote_host" --><br>
> Remote Address: <!--#echo var="remote_addr" --><br>
> Remote User: <!--#echo var="remote_user" --><br>
> Content Type: <!--#echo var="content_type" --><br>
> Content Length: <!--#echo var="content_length" --><br>
> HTTP Accept: <!--#echo var="http_accept" --><br>
> HTTP User Agent (Browser): <!--#echo var="http_user_agent" --><br>
> HTTP Cookie: <!--#echo var="http_cookie" --><br>
> Unescaped query string: <!--#echo var="query_string_unescaped" --><br>
> Query String: <!--#echo var="query_string" --><br>
> Path Info: <!--#echo var="path_info" --><br>
> Path Translated: <!--#echo var="path_translated" --><br>
> Referer: <!--#echo var="referer" --><br>
> Forwarded: <!--#echo var="forwarded" --><br>

An incomplete "story" but enough to get one started.

When reading the manual (and yes - RTFM), note also the use of variables which
start "Redirect_"... and why they exist.