> 2.If the answer to the above question is YES? The > Handler will add headers,footers for everything. What > do I need to do to apply the handler logic just to the > requested page and return the remaining files that are > needed to complete the requested page as they are?
In the Eagle book (as well as a Perl Journal article) there is an example of a Apache::Header/Apache::Footer. CPAN doesn't show them right now. But you could implement them as filters using Apache::Filter to mark up each document on its way out, based on URI. > 3. When I move these JS files outside the /en/course > URI they seem to work? But now when I put them with > in? It just displays the Javascript code like simple > text on the browser. <SCRIPT SRC="/en/course/one.js"></SCRIPT> ... or you could template them in directly, since you're playing w/ the content already. > 4. In the Logging Phase, I need to store the last > requested page as a bookmark. So if the user logs out, > and logs back in it takes him to the same page. Since > the html files are made up of some many requests to > other files, it stores the last file it requested. It > may be path to an image file,style sheet file etc... > Is there any way I can circumvent this problem? You could use a cookie, issued with each document, noting what url they are on right now?? Logging it (storing it) and then reading it back are bound to be waaaaay too much work. HTH! L8r, Rob
