Another knock-on effect of the change from .htm to .html for generated output

Another knock-on effect of the change from .htm to .html for generated output
Richard Kaye
All

Oct 1, 2026 @ 06:26am

Just putting this one up here as an fyi. File it under potential breaking change for folks migrating from WWHB.

For context, my help content is deployed behind my app login. Once logged in there's a help button in my nav that takes the user to a context-sensitive help topic (Sidenote: thanks for fixing the ?topic= thing so quickly!) A user reported getting a 403 when toggling search modes between simple and detailed. The URLs for the earch toggle are constructed like this:

https://<my website>/help/#searchAdvanced
https://<my website>/help/#searchSimple

After a bit of head-scratching I added a new default document entry to the root help folder for index*.html* in IIS and that eliminated the 403. There is a bit of a flash the first time search modes are toggled but the security problem is solved.