I would like to know how I can set up my sub-site, of a Publishing Site Collection, to include all the files it needs to run on its own? I don't want it to access any global resources. I would like full functionality from http://myserver/mysitecollection1

Is that possible? 

Base images are using a link that contains http://myserver/_layouts/... and ScriptResource.axd is also accessed from the root of the web application. I want them to be included and used from http://myserver/mysitecollection1

Thanks

No matter how many images and resource files we move, there will be some internal references for certain functionality like explorer view or drag and drop feature to access some resource from top level site collection.

I am not sure whether it is possible for sure or not, but in my experience, i have seen some issues, trying similar thing not immediately but later into the project.

Thanks.

I was doing some more research. Do you think creating a Publishing Site collection, in an Explicit inclusion Managed Path, would give me the functionality I need?

I would want to create it at http://myserver/mysitecollection2 and I know that I wouldn't be allowed to create any sub-sites, but do you think that would solve the problem?

I have only used Wildcard inclusion Managed Paths.

Update 4:23pm

Never mind. Already tried it and it does the exact same thing...

The following resources are always pointing to the root:

/_layouts/15/images/... etc.

/Style%20Library/en-US/Themable/Core%20Styles/... etc.

/ScriptResource.axd

• Edited by brianhull1 8 hours 12 minutes ago Update