6.0.0-beta1
9/19/25

[#1515] LDAP, contact update in firefox, encoding, __key
Summary LDAP, contact update in firefox, encoding, __key
Queue Turba
Queue Version 2.0.2
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester m.zdila (at) episoftware (dot) com
Created 03/09/2005 (7499 days ago)
Due
Updated 05/05/2005 (7442 days ago)
Assigned 04/16/2005 (7461 days ago)
Resolved 05/05/2005 (7442 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/05/2005 12:50:53 PM Jan Schneider Comment #3
State ⇒ Not A Bug
Reply to this comment
No feedback.
04/16/2005 12:04:08 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
I'm having a hard time to understand what *exactly* you are talking 
about. Can you please first try the latest Turba CVS code to see if 
this still happens, and then try again to explain in detail what is 
happening and where?
03/09/2005 09:58:52 AM m (dot) zdila (at) episoftware (dot) com Comment #1
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ LDAP, contact update in firefox, encoding, __key
Queue ⇒ Turba
Reply to this comment
After creating a contact in the addressbook (LDAP) with central 
european (CE) characters it is stored OK. The key (eg. cn) contains CE 
characters which are stored into the LDAP in the UTF-8 encoding.



Now, if I try to edit the contact and:

1. usinf Mozilla Firefox 1.0

2. using iso-8859-2 encoding

3. the __key contains CE characters



The generated page with the form contains hidden input "key" with the 
value that contains UTF-8 characters not correctly recoded to 
iso-8859-2. After the form submission the request variable 
($_POST['key']) contains invalid value and the contact can't be found 
in the LDAP.



using Konqueror, MSIE, or when using english (American) - it works.

Saved Queries