![]() ![]() Though I could perhaps handle the persistence issue with permanent aliases for the files once the new template rollout is complete. Mod_alias can alias /includes to /new/includes but how do I get the conditional subfoldera in there? (The Alias directive only works within the server and virtual host contexts.)Ĭan I somehow pass the Remote Condition through to mod_alias using the Pass Through flag?Īny other options? The only workable alternative I could think of was to call my new template files by different names to those of my old template files and host them in the existing /includes directory, but because the original names need to persist for other reasons (they are resources used by other sites not run by me) they will need to be changed back, which is no saving of effort over changing the directory part of the path reference. ![]() Mod_rewrite does conditional matching, but can't rewrite includes as these are handled within the server filespace not the webspace. Exposed headers are extra headers servers can include in a response. Expose headers: By default, not all response headers are exposed to client-side JavaScript code in a cross-origin request. Controls the Access-Control-Allow-Headers response header. for material in subfoldera only I want to be able to use '/includes' now and for this to be resolved as '/new/includes'. Custom footer text Whilst small files can be uploaded to forum posts, if you have a custom theme or module to contribute please add it on the 'Add-ons' page. Allowed headers: List of the headers allowed in cross-origin requests. ![]() However, I want the files at /subfoldera to use the same include reference paths as files using the old templates so that when these files are moved out all over the webspace, and the includes at /new/includes replace those at /includes, it is not necessary to change all the include references within the files from /new/includes to /includes. The files which call these are held only in one directory, /subfoldera. I am now developing a new set of template files, to eventually replace the existing ones. Files calling these includes are all over my webtree and use root-relative references to find them. The site's pages use a set of template files (header, footer, etc.) held in the /includes directory. I have an apache 1.3 site running on Linux. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |