2 Replies Latest reply: Feb 20, 2013 6:30 AM by Ilgiz valiev
Ilgiz valiev Level 1 Level 1

When I creating new CalDAV calendar with login that contains non-ASCII characters, iCal calendar doesn't sent Authorization header in a request package.

When I use ascii login http request contains header like:

 

Authorization: Digest username="Art", realm="TeamWox", nonce="DFEBA3CD93184f389CAAAE84F1E0177D", uri="/caldav", response="511573b614eff34270e7b99b4b8a7b9b", cnonce="1b3aae2d7cd48bfa8aceadc62ff56006", nc=00000001, qop="auth"\r\n

 

If I add non-ASCII charcters I didn't receive it.

Can You explain this, please?


iPhone 4, iOS 6.1.1, iCal
  • Roger Wilmut1 Level 9 Level 9
    expertise.itunes
    iTunes

    Many login systems will only handle plain text, and you should stick to that - upper or lower case letters, and numerals - no odd punctuation characters or diacriticals.

  • Ilgiz valiev Level 1 Level 1

    Digest autification send information in UTF-8.

    When I analyze packages with WireShark I see that for example Windows WebDAV sends this text in UTF-8 encoding, and all characters were sended correctly regardless of language.

    iCal just doesn't send Authorization header if characters no in ASCII (0-127).