Hi list,
I recently started using pylons so I'm not sure what I might be
missing here but, its my instinct that the following issue is probably
a bug.
I want to use repoze.who.plugins.baiscauth; the end result is that
required auth results in a WWW-Authenticate header being sent which
triggers that fugly login dialog window in your browser ( or allows
curl, wget and other useful applications to connect using "server
authentication"). After countless hours of thinking I has bad configs
with my repoze setup, I started to look elsewhere... in the end I
found out that commenting out the StatusCodeRedirect assignments in
middleware.py fixed the problem.
Ultimate the basicauth request headers was not being forwarded with
the environment to the error controller so the header did not exist
and my fugly box was no show.
Additionally my errors 404, 401 etc get picked up via
request.environ.get('pylons.original_response') in my error controller
and create a malformed html page (an html document inside the div node
of another html document of the error template).
Pylons has been great to me so far and I'm loving it. But the error
handler does not seem to be doing things in a why I would expect. Like
using render if it can.
Is there another ErrorHandler/StatusCodeRedirect object or way of
configuring error management which would have the original_response as
just the headers w/status and so forth and allow me to do it my way
inside my own /real/ error controller. Or does any *good*
documentation including important gotyas for doing this myself?
I'm using pylons '0.10rc1' with python 2.6.4. My project may been from
0.9.7
Thanks
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
