On Jul 21, 3:10 am, Damjan <gdam...@gmail.com> wrote:
> > [Fri Jul 17 19:01:43 2009] [error] [client 192.168.1.100] TypeError:
> > sequence of string values expected, value of type literal found,
> > referer:http://192.168.1.100/
>
> This seems like the common error in middleware to not return strings
> but probably a number in your case.
>
> You could try to wrap different middleware (AurhKit?) with
> wsgiref.validate to check it's conformance to the WSGI standard.
>
> http://docs.python.org/library/wsgiref.html#module-wsgiref.validate
FWIW, this isn't a problem with response headers, where returning
types other than strings is often a problem, but in the type of values
yielded by the returned iterable, or as contained in the list
returned. They should be strings and instead it is returning something
else.
I am not actually sure that wsgiref.validate properly checks that the
iterable yields strings, so it may not pick it up correctly. At least
my tests indicate that returning a non string from the iterable just
gets passed straight through wsgiref.validate and still chokes on
mod_wsgi. This could be viewed as a bug/deficiency in
wsgiref.validate. Doesn't seem to be fixed in Python 3.1 either.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to
pylons-discuss+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
