We are using Session-based authentication and have multiple websites. Some are HTML-based.
Is there a way of creating a single, generic ‘Page not found’ response? I have attempted using a WebSiteRule > HTTP Response Header doc and have attempted the DomCfg.nsf database - I could get neither to work.
DOMCFG.NSF - The documentation indicates that “Domino does not use customized error pages to display errors when authenticating with the server or accessing a database if session-based name and password authentication is enabled.”
If you use a website rule I believe it will work. Just read the link on my previous response. I have created rules for HTML-base (non-NSF) on my webserver.
could you try to explain, bit by bit, how creating a http header will solve the problem? Im not sure I’m getting your point. I used to have the httpd.cnf file re-directing the user to a html page with javascript, that performed a search - and through this search guided the user to a specific page, based on the last parameter of the url.
E.g. xxx.dk/media → search for media in a specific keyword on documents → present dokument…
As I see it there is no point at all to use the http header to try to create a custom 404 response page.
I have not been able to conclude that there are a way to solve this problem in domino. I want to be able to customize the 404 response page, so that I can catch all strange URLs people are using and pressent tem with a meaningful page.
There is nothing custom about a 404 page if you use the domcfg.nsf approach. The domcfg approach does not know the difference between a 404 and say a 403.
I used the header to allow the form show special text because of a 404 was reached.
I created a header with a special field set to the header for the 404. That way when the error form is called through the domcfg.nsf error mapping, the message is custom via the form. (I had some hide when going on to show certain things based on the header fields.)
What others have mention is true, but is using the header to pass data to the error form. The error mapping via domcfg.nsf is very general.
I’ve tried using HTTP response header rule as you suggested. I can get it to work in an almost satisfactory way by creating a “HTTP Response header” rule with the following data:
Incoming URL pattern → /*
HTTP response codes → 404
Expires header → Do not add header
(custom header) → Name = “Refresh” / Value = “0;URL=/404/404.html”
This basically works like a tag, but it’s not ideal, as users see the default 404 error message flashing before they are redirected to our custom 404 page.
Is any other way to do this? What is the special field set you used to redirect to the domcfg.nsf error mapping?
Note that the redirection using HTTP Repsonse Headers does not seem to work when the setting “Show friendly http error messages” is enabled in Internet Explorer advanced settings.