08-08-2021, 08:14 AM
You're right, I initialize the content handler this way and I also mean the standard error page with error code 404 (Not found).
I would like to capture the website scanning for nonexistent paths and files without changing the behavior of the server.
According to the version history of IW15.2.33, this seemed to me a useful way.
"Content Handlers: allow registration of a “catch-all” content handler for any path and document (should be registered with an asterisk, e.g., THandlers.Add(”, ‘*’, TMyContentHandler.Create). Instead of returning 404 for any unknown path you can, for instance, redirect the request to a valid page/form/content handler/etc. (See TContentRedirect examples)."
Maybe you can give me a hint how I can do that.
But still,
https://Mydomain.com/URLBase/
https://Mydomain.com/URLBase
both should work for each browser, also without any catch-all content-handler.
I would like to capture the website scanning for nonexistent paths and files without changing the behavior of the server.
According to the version history of IW15.2.33, this seemed to me a useful way.
"Content Handlers: allow registration of a “catch-all” content handler for any path and document (should be registered with an asterisk, e.g., THandlers.Add(”, ‘*’, TMyContentHandler.Create). Instead of returning 404 for any unknown path you can, for instance, redirect the request to a valid page/form/content handler/etc. (See TContentRedirect examples)."
Maybe you can give me a hint how I can do that.
But still,
https://Mydomain.com/URLBase/
https://Mydomain.com/URLBase
both should work for each browser, also without any catch-all content-handler.