On Wed, Dec 13, 2006 at 12:16:30AM +0100, Daniel McBrearty wrote:
Am migrating from an old system which used Basic Auth, to this plugin.
As mentioned in a previous post, using
password_type = crypted
means that the old passwords still work. Nice ...
But reading the docs for crypt I just
although ... there might be a related problem that makes restricting
to ASCII make sense. If usernames are also UTF8, will there be
potential problems using them in URLs? I know UTF8 in urls have been
discussed a lot, but I've no idea what the current state of play is
(does it work well on all
I know UTF8 in urls have been
discussed a lot, but I've no idea what the current state of play is
(does it work well on all platforms).
Yes. http://host/path/to/something/%xx%xx%xx%xx%xx%xx%xx%xx%xx/...
The %xx's are the utf-8 octets. Catalyst will understand this just
fine; we even have
thanks Jonathan. I looked up on the W3C site and saw that this was how
it should work, and had it on my list to see if cat would be all right
with it. I'd have been surprised if it wouldn't, TBH ...
it's taken me quite a while to get up to speed on cat/dbix/tt ... a
lot of new stuff to learn,
or maybe it's even simpler ... it looks like
C::P::A::Password::_check_password tries all methods until it
succeeds, depending on User::supports ... so I guess that saying
$user::supports( qw/crypted hashed/) somewhere should do it?
sorry for clogging up the list with my ramblings ... perhaps I
