Hello Daniel, > that's surprising. > > Isn't there a way to tell browser and server to use e.g. UTF-8 encoding to > circumvent somehow?
HTTP protocol does not describe any standard and interoperable method that could allow to specify the encoding of nonUS-ASCII symbols in passwords. Different clients / browsers use different encoding, in fact. The only possible workaround for now is to exclude such characters from passwords or switch to Integrated Windows Authentication. -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
