It could be that IE cached the 500 page, whereas Firefox didn't.
Try:
<Ctrl><F5>
in IE. It force-refreshes the page by dumping the browser's cache for
said page :)
Sent from my iPhone
On Jul 9, 2008, at 20:09, gt7658b <[EMAIL PROTECTED]> wrote:
>
> The previous information was not accurate. Actually it works fine
> with firefox, but cause apache 500 error on IE.
>
> On Jul 9, 9:28 pm, gt7658b <[EMAIL PROTECTED]> wrote:
>> Thanks for the help, I was able to make it work. It was due to the
>> fact that memcache.py was not under PYTHONPATH.
>>
>> There is still one puzzle. As suggested by you, CacheMiddleware
>> should
>> come before SessionMiddleware (also recommended by the django doc.).
>> If I do that as follow, I will get an apache internal server error.
>>
>> //this order did not work
>> MIDDLEWARE_CLASSES = (
>> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>> 'django.middleware.cache.CacheMiddleware',
>> 'django.contrib.sessions.middleware.SessionMiddleware',
>> 'django.middleware.doc.XViewMiddleware',
>> 'django.middleware.common.CommonMiddleware',
>> 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
>> )
>>
>> //this works
>> MIDDLEWARE_CLASSES = (
>> 'django.contrib.sessions.middleware.SessionMiddleware',
>> 'django.middleware.doc.XViewMiddleware',
>> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>> 'django.middleware.cache.CacheMiddleware',
>> 'django.middleware.common.CommonMiddleware',
>> 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
>> )
>>
>> On Jul 9, 12:19 pm, "Norman Harman" <[EMAIL PROTECTED]> wrote:
>>
>>> gt7658b wrote:
>>>> Hello, I tried to use memcached as follow. BTW, memcached is
>>>> running
>>>> as seen from top command on server.
>>
>>>> CACHE_BACKEND = 'memcached://127.0.0.1:11211/'
>>>> # CACHE_BACKEND = 'dummy:///'
>>>> CACHE_MIDDLEWARE_SECONDS = 60*30
>>>> CACHE_MIDDLEWARE_KEY_PREFIX =''
>>>> CACHE_MIDDLEWARE_ANONYMOUS_ONLY = True
>>
>>>> MIDDLEWARE_CLASSES = (
>>>> 'django.contrib.sessions.middleware.SessionMiddleware',
>>>> 'django.middleware.doc.XViewMiddleware',
>>>> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>>>> 'django.middleware.cache.CacheMiddleware',
>>>> 'django.middleware.common.CommonMiddleware',
>>>>
>>>> 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
>>>> )
>>
>>>> However, I got 500 error. If I switch to CACHE_BACKEND =
>>>> 'dummy:///',
>>>> our web site worked just fine.
>>
>>> CacheMiddle ware should come before
>>> SessionMiddlewarehttp://www.djangoproject.com/documentation/cache/#order-of-middleware
>>>
>>> ...
>>
>>> Is the 500 from Django builtin server or from some other server?
>>
>>> Do you have debugging and what not turned on? you should be
>>> getting more
>>> info(traceback) than just a 500.
>>
>>> Have you read and understood the requirements for using memcached
>>> with
>>> Djangohttp://www.djangoproject.com/documentation/cache/#memcached
>>
>>> Have you tried using python memcached libs by hand in Python shell
>>> or
>>> writing little test scripts not using Django?
>>
>>> You have provided too little information for anyone to tell you
>>> what is
>>> wrong. But with the above information and a little investigation
>>> you
>>> should be able to figure it out on your own :)
>>
>>> --
>>> Norman J. Harman Jr.
>>> Senior Web Specialist, Austin American-Statesman
>>> ___________________________________________________________________________
>>> You've got fun! Check out Austin360.com for all the entertainment
>>> info you need to live it up in the big city!
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
