New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workaround for unwanted error messages #105

Open
vibs29 opened this Issue Jul 20, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@vibs29

vibs29 commented Jul 20, 2015

Hunchentoot is meant to hide error details from web users unless
*show-lisp-errors-p* is overridden to true. But it doesn't always
hide them.

Here is how hunchentoot renders errors:

a) if there's an error template html file use it, otherwise
b) cook up a message whose level of detail depends on *show-lisp-errors-p*
   and *show-lisp-backtraces-p*

As distributed, hunchentoot contains a 500.html error template file,
so that is used and there is no need to cook up a message in code.

The provided 500.html error template prints out the error message
and backtrace, regardless of *show-lisp-errors-p* and
*show-lisp-backtraces-p*.

Refs:

acceptor.lisp -> defgeneric #'acceptor-status-message documentation
acceptor.lisp -> #'make-cooked-message -> +http-internal-server-error+ clause
www/errors/500.html

Workaround:

Set your acceptor's error-template-directory to nil, causing
hunchentoot to bypass (a) above.

(make-instance 'easy-acceptor :port 8000 :error-template-directory nil)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment