Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 14 Aug 2008 22:41:51 +0400
From: Vasiliy Baranov <Vasiliy.Baranov@Sun.COM>
Subject: request_rec.filename alteration
Sender: Vasiliy.Baranov@Sun.COM
To: modules-dev@httpd.apache.org
Message-id: <48A47C6F.9010603@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)

Hi,

I am trying to write a module that internally translates 
"/foo/bar/XXX/..." in document paths to "/foo/bar/YYY/...", where 
"/foo/bar" is a constant and YYY is a function of "/foo/bar" contents on 
disk _and_ authenticated user name. Since the translate_name phase 
precedes check_user_id (authentication) phase, doing my translation in a 
translate_name hook is out of question. On the other hand, when I am in 
a fixups hook, I am able to alter request_rec.filename as needed, but 
then someone, most likely core.c line 3631 (httpd 2.2.9), notices that 
the original document (in "/foo/bar/XXX/...") does not exist, and issues 
FILE_NOT_FOUND. What would be the right way to approach this? Doing this 
stuff at the end of authentication phase? Internal redirects? I think I 
can do an internal redirect from a fixups hook, however, it seems 
somewhat difficult to construct a correct URI for passing to 
ap_inernal_redirect() there - in my case "/foo/bar/XXX/..." itself may 
be a result of one of many Aliases.

Thank you,
Vasiliy