Nik, this is a great fix, thank you! I ended up trying a little different approach because I could not gaurantee that our users were going to access child portals using one of the subhost files, and the problem still appeared if they just accessed the portal by tabid.
Here is another Core Hack that seems to be solving this problem for specific files:
(I will use LHNavi as an example below)
1) In your Web.Config under the <appSettings> section, add the following Key:
<add key="Auth-Exclude" value="file1,file2,file3" />
* You would insert the absolute path(s) to the file(s) that you want to exclude from authentication in a comma delim list.
For LHNavi this might look like:
<add key="Auth-Exclude" value="/desktopmodules/leftnavi2/leftnavicss.aspx,/desktopmodules/leftnavi2/navileftJs.aspx" />
2) In the Global.asax.vb file at the top of the file, (above the "Namespace DotNetNuke" line) add the following import:
Imports System.Configuration
3) In the Global.asax.vb file at the bottom of Sub Application_Start add the following lines:
' Added for Auth-Exclude Fix
Application("Auth-Exclude") = ConfigurationSettings.AppSettings("Auth-Exclude").ToString.ToLower()
4) In the Global.asax.vb file at the top of Sub Application_AuthenticateRequest add the following lines:
Dim CurFile As String = HttpContext.Current.Current.Request.Url.AbsolutePath.ToString.ToLower()
If Not (InStr(Application("Auth-Exclude").ToString(), CurFile) > 0) Then
5) In the Global.asax.vb file at the bottom of Sub Application_AuthenticateRequest add the following line:
(place this directly above "End Sub"...)
End If
Recompile... you might need to reset the site so that the cache is cleared and Application_Start is called.
I found that by blocking that section completely for specific files only, then everything seemed to work great.
Thanks again,
Jim Scheitel
Web Developer
Knife River Corporation