Wsgi Traceback on Django 1.8

[lza...@ucs.br]

Error on Django 1.8:

My site do not use session and cookies, its basic a static site and some forms.

Django 1.7.7 it's OK.


Traceback (most recent call last):
  File "/usr/local/envs/wscep/lib/python3.4/site-packages/django/core/handlers/wsgi.py", line 195, in __call__
    for c in response.cookies.values():
AttributeError: 'str' object has no attribute 'values'

Enviado via UCSMail.

[Curtis Maloney]

At a guess, one of your views is returning a string instead of a HttpResponse object.

This is the wrong forum for this question.  This list is for discussing the development _of_ django, not _with_ django.  Your question belongs in django-users.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7bb3179f-1d0a-47cf-a46a-f1b7d0ed47a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Graham]

This query came up on IRC a few days ago. I believe it was solved by clearing the site's cache. This is one of the recommended steps in "How to Upgrade Django."

https://docs.djangoproject.com/en/dev/howto/upgrade-version/

[lza...@ucs.br]

Hi Tim,

You are right, this view use a @cache_page decorator and after cleaned the cache the problem was solved. I would never imagine that I must clean cache on update to 1.8.

Sorry by post here, but I touth that was a seriosly bug on wsgi module.

By.

Enviado via UCSMail.