Errors low in the stack provide unhelpful text.

[Issac Kelly]

I had an error in my cache configuration for a full-site cache setup.

Here are the relavent settings:

MIDDLEWARE_CLASSES = [

'django.middleware.cache.UpdateCacheMiddleware',
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'pagination.middleware.PaginationMiddleware',
'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
'django.middleware.cache.FetchFromCacheMiddleware',

]
CACHES = {

'default': {

'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
'LOCATION': 'unique-snowflake'

}

}
CACHE_MIDDLEWARE_ALIAS = 'somethingelse'
CACHE_MIDDLEWARE_SECONDS = 90 * 60
CACHE_MIDDLEWARE_KEY_PREFIX = 'issackelly_com_mw'

With these settings I got a traceback in the runserver console, but the only thing that was displayed in the browser was the following:

"""A server error occurred. Please contact the administrator."""

[chomik]

At the moment when this exception is raised there is no request object available. Traceback error page would have to be created by hand and returned bypassing normal request dispatching.

Creating response would involve complex exception handling and would prevent proper exception propagation.

It is safer to leave it as it is.

[Aymeric Augustin]

The error message isn't generated by Django, I suppose it's displayed by your browser when it doesn't even receive an HTTP response.