Hi Everyone,
Sorry if my earlier post was confusing.
Basically, if you setup a workarea as an application in IIS (which is required to render .ASPX pages) then the iwproxy_isap.dll preconnect entries are no longer processed. Basically you get errors like this in your isapi log file:
Debug mode for iwproxy_ISAPI.dll log file yields:
OnUrlMap
ThreadId: 6204
URL: /iw-mount/default/main/BWH/Internet/Demo/WORKAREA/redesign/templateElements/header.htm
PhysicalPath: Y:\default\main\BWH\Internet\Demo\WORKAREA\redesign\templateElements\header.htm
Buffer Size: 261
String length: 79
SCRIPT_NAME: '/iw-mount/default/main/BWH/Internet/Demo/WORKAREA/redesign/demo/introduction.aspx'
PATH_INFO: '/iw-mount/default/main/BWH/Internet/Demo/WORKAREA/redesign/demo/introduction.aspx'
OnUrlMap, constructed ppath url is '/iw-mount/default/main/BWH/Internet/Demo/WORKAREA/redesign/templateElements/header.htm'
OnUrlMap, Skipping rewrite because PhysicalPath is already areaized (virtual directory)
^^^^^^^^^^^^^^^^^^^^^^^^
Notice the line above, it tells me that its never even bothering to rewrite the path because it says the workarea is already "areaized" which to me, means its an application root. So its not even following the regex's in iw.cfg.
So am I right in that I can't have Server Side Includes (SSI) remapped using iwproxy_isapi.dll for an area that is a .net application root?
That is my theory. Its telling me that its ignoring it.
Any thoughts? I was going to call support as well on this one.
My backup plan is for each branch to have a copy of the /bin (et al Visual Studio ) folders and lock them down using "private" setting.
Any thoughts on that as well?
I really appreciate all the help over the years that I've gotten in this forum.
Keith.
Additional Info --------------------------------
My branch structure is:
Branch1
/workarea <-IIS virtual directory/.net application
/somepage1.aspx
Branch2
/workarea <-IIS virtual directory/.net application
/somepage2.aspx
Branch3
/workarea
/bin <-- the .NET bin folder
/templateElements
all branches publish to the same site, and I put /bin into its own folder that we (IS) control and publish, but I want other workareas/aspx pages to grab SSI includes (/bin or /templateElements) from Branch 3.
e.g. In my .aspx page I have virtual includes like this:
<tr>
<td><!-- #include virtual="~/templateElements/header.htm" --></td>
</tr>
This utilizes ASP.NET's "~" directive which resolves absolute paths to files. So this file should come from Branch 3 but doesn't.
I setup iwproxy plugin remap setup like this to redirect anything looking for templateElements and it doesn't work
(I've done this tons of times and it works fine for regular asp pages)
[iwproxy_plugin_remap]
_regex=(.*)/templateElements/header\.htm=$1/main/BWH/Internet/WebDevelopmentInternet/WORKAREA/content/templateElements/header\.htm
But when I try to view the page from say Branch 1, I get:
Parser Error Message: Could not find a part of the path "Y:\default\main\BWH\Internet\Demo\WORKAREA\redesign\templateElements\header.htm".
Source Error:
Line 57: <!-- Header -->
Line 58: <tr>
Line 59: <td><!-- #include virtual="~/templateElements/header.htm" --></td>
Line 60: </tr>
Line 61:
Edited by kvargas23 on 01/23/06 06:50 PM (server time).
