|
| |
|
|
Wage Slave
Posts: 24
From: None
Status: offline
 |
Host Header - Path Problems - 1/17/2003 15:15:55
I' m having trouble with the template path in the Search Form component, specifically when a site can be addressed two different ways due to a host header.
We' re hosting a number of sites on a server running NT and release 1.2 of the FP2000 extensions. All sites are FrontPage subwebs under the virtual server " Default Web Site" , and their files reside in subdirectories under D:\inetpub\wwwroot\. Administrators of " mysite" open it as http://our.hostserver.com/mysite/ in FrontPage and users address it the same way in their browsers.
At one point, the owners of " mysite" acquired their own alias (host header). To enable it, I created a virtual server " my.site.com" in MMC and set its path to D:\inetpub\wwwroot\mysite, the directory of the existing FrontPage subweb under Default Web Site. After that, you could address the site in your browser as either http://our.hostserver.com/mysite/ or http://my.site.com/. Site administration continued to be done through http://our.hostserver.com/mysite/ and could not be done through http://my.site.com/ because FrontPage won' t allow extensions to be applied to two different sites mapped to the same directory.
Both methods of addressing worked fine except when it came to pages using the Search Form component. It would function normally if you addressed the page through http://our.hostserver.com/mysite/ but a search done from http://my.site.com/ always produces this error: " The template file can not be found in the location specified by ' CiTemplate=' " in the IDQ file under _vti_script. I checked the IDQ and found the citemplate value prefixed with the subweb name: " /mysite/_derived/search.htm0.htx" . The template path fails because the " mysite" subdirectory is incorporated in the " my.site.com" mapping and doesn' t exist under it.
I can fix this with a klugey bit of ASP work in the search page but there has to be a better solution.
- Can you have this kind of multi-addressing without exposing yourself to path problems?
- Is there a better architecture for the sites?
- Is there a better way to configure host headers?
Wage Slave
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
