Tim's answer will prevent indexing, but the code you posted seems to be for denying people access to your documentation until they have logged in. You might have business reasons for that, e.g. to prevent potential buyers from evaluating the functionality without being guided by a sales person, or for security (denying hackers information about the system), or simply to track who is reading which help topics.
As it stands at the moment, once someone has a link to any page of the documentation, they can browse any of your HTML user guides (e.g. I reached CIM GOLD, GOLDWriter, GOLDMiner). However, the guides that have been published as ASP pages (e.g.
GOLDPrint) are blocked, because the server does a 302 redirect to the default login screen. I suppose you are looking for similar security for all your guides?
If so, it might be as simple as republishing your web guide with different filenames so that they are processed by ASP.NET on your server. I don't have a ton of experience with this but these steps worked on my local (IIS 8) server:
- In Help & Manual's HTML Export Options set the Extension for HTML files to ".aspx". You'll have to type this manually in the field, it's not one of the listed values.
- In H&M's WebHelp publishing task, set the Index page to "default.aspx".
- Publish and copy all the files to an ASP.NET folder on your IIS web server. I won't attempt to explain how to set this up: I'm not an expert, you are running an older version of IIS, and anyway there must be someone in your web team who already knows this stuff.
- If you don't already have a 'web.config' file in the folder, a minimal one for test purposes might be:
Code: Select all
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Now point your browser at the folder and see what happens. It may be that the entire server is already configured to force a login, in which case your code fragment won't be needed. On that other hand if it is needed, try putting it at the beginning of your HTML template, above the <%DOCTYPE%>, and publish to aspx as above. Note that your secure.goldpointsystems.com domain is being hosted on IIS 6 whereas
http://www.goldpointsystems.com is hosted on IIS 8.5, so that might account for some differences of behavior.
Good luck...