Hi Timmy!
Timmy Chan wrote:
> my current workflow for FriendlyFormPlugin is
>
> user goes to page, needs permission, gets 401
> repoze.who sends it to login_form_url
> user inputs data
> user gets sends to post_login_url, gets 401
> gets sent to login_form_url again
>
> is this a good method?
New submission from Nuno Teixeira :
Index: docs/narr/unittesting.rst
===
--- docs/narr/unittesting.rst (revision 9323)
+++ docs/narr/unittesting.rst (working copy)
@@ -115,7 +115,7 @@
of a :term:`Configurator`, including its
New submission from Nuno Teixeira :
To avoid SAWarning messages like below request to DB should be unicoded:
SAWarning: Unicode type received non-unicode bind param value 'foo'
nteixe...@nteixeira-desktop:~/co/repoze.whoplugins.whoalchemy$ svn diff
Index: repoze/who/plu
Olá Gustavo,
Thanks for your fast reply and your suggestions! ;)
That occurs when using repoze.who.plugins.cookie.InsecureCookiePlugin as
an identifier.
As I can see cookies are stored as ASCII strings so
cookie.value.decode('base64') (#1 @ line 25) returns an ASCII string
which is passed to
New submission from Nuno Teixeira :
I think that encoding cookies data could be useful. My usecase is related with
SQLAlchemy that avoid the use of non-unicode strings on queries.
--
files: r9728.diff
messages: 426
nosy: nteixeira
priority: feature
status: unread
title: Support
Nuno Teixeira added the comment:
Added tests for full coverage
__
Repoze Bugs
<http://bugs.repoze.org/issue155>
__Index: repoze/who/plugins/cookie.py
===
---
