Geoff,
That's not Spanish characters, come on... It's just ASCII garbage. :-)
-S.
Geoff Longman wrote:
Ok. looking up the stack in the debugger it is obvious that Acegi is
not the culprit. The string is screwed from the get go.
Geoff
On 1/17/06, Geoff Longman <[EMAIL PROTECTED]> wrote:
This is the first time I've run into this!
A login page. The form submits directly into Acegi for authentication.
The username is: aáéÉíóúñÑ¿¡«» (I'm told these are spanish characters :-)
But when the string arrives in the DAO that looks up the user it looks
like this...
aáÃ(c)ÉÃóúñÃ'¿¡«»
Now when I use the Fiddler proxy I can see the string encoded for
transport as this:
j_username=a%C3%A1%C3%A9%C3%89%C3%AD%C3%B3%C3%BA%C3%B1%C3%91%C2%BF%C2%A1%C2%AB%C2%BB
Luckily this app is a reimplementation of an ASP app and we have
access to the legacy app.
When the legacy app login page submits the username looks like this in proxy...
strUserName=a%E1%E9%C9%ED%F3%FA%F1%D1%BF%A1%AB%BB
I'm at a loss to explain why the encoded username would be different.
Same browser, the only diff is that one is ASP and one is
Java/Tapestry (on Jetty but the same problem shows on Tomcat).
Any ideas?
Geoff
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog: http://jroller.com/page/glongman
Feature Updates: http://spindle.sf.net/updates
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog: http://jroller.com/page/glongman
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
