I do not want to publish the install folder and I excluded it from the project, however it is referenced in the global.asax and expects the install to be there. Can I just ditch all nop references in the global.asax script block or are there references that are crucial to the application ...
... then can one add this little SEO helper to the global.asax to ditch the www from the domain name which is running on the production server's present non-nop application (which will be replaced by nop 1.8)?
public void Application_BeginRequest(object sender, EventArgs e)
{
// Fires at the beginning of each request
if (HttpContext.Current.Request.Url.ToString().ToLower().Contains("http://www.foo.com")) {
HttpContext.Current.Response.Status = "301 Moved Permanently";
HttpContext.Current.Response.AddHeader("Location", Request.Url.ToString().ToLower().Replace("http://www.foo.com", "http://foo.com"));
}
}
last, I usually like to put the admin in different subdomain or even different server for security but this is not an option for the site I am working on. But if I at the least change the name of the administration folder and references to it in the source code and recompile it may thwart the casual curious. correct?