I've read the page "packages/acs-tcl/tcl/request-processor-procs.tcl". I could understand some points but It's still sort of chinese to me. =)
ad_proc -private rp_resources_filter { why } {
This filter runs on all URLs of the form /resources/*. The acs-resources package
mounts itself at /resources but we short circuit references here in order to
maximize throughput for resource files. We just ns_returnfile the file, no
permissions are checked, the ad_conn structure is not initialized, etc.
There are two mapping possibilities:
/resources/package-key/* maps to root/packages/package-key/www/resources/*
*******************8
" Keep in mind that if you do an internal redirect to something other than
the current directory, relative links returned to the clients
browser may be broken (since the client will have the original URL).""
I understood "internal redirect" as if i try to include pages those are "i don't knnow" or if the pages needs permission. Is that correct?
Another thing is...
I couldn't match this with the header metatags. I mean, how do they go to the final page, on the client side(i.e. on the user's browse). Can you tell how they go to the page? Where are the metatags actually located?
I want to track and debug the whole process that it takes since the begining(i.e. the first step) to the end(i.e. user's browser).
