0003255: cardDAV: remote adressbooks do not work with @ in the username - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0003255	SOGo Connector	with SOGo	public	2015-06-14 18:33	2018-03-17 01:16

Reporter	evh	Assigned To	ludovic
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	suspended
Platform	Fedora 20 64bit	OS	Fedora Linux	OS Version	20
Product Version	24.0.4

Summary	0003255: cardDAV: remote adressbooks do not work with @ in the username
Description	Thunderbird: 31.7.0 Sogo Connector: 24.0.2 ( interesstingly, no updates shown) Lightning: 3.3.3 It looks like the "@" is misintrepreted as the @ from such an url: "http://user:password@domain/...." which it isn't, as it's clearly in the URI part. Actual results: TB ( or Lightning or Sogo ) does not even try to connect to the server. Expected results: TB ( or Lightning or Sogo ) should work normally, as the same CalDAV url with an @ in the username works as expected.
Steps To Reproduce	Steps to reproduce: Version: 31.7.0 Linux Fedora 20 64bit if you use a remote addressbook url like : http://cal.domain.com/index.php/addressbooks/xxxx@servicename/default/ TB ( or Lightning or Sogo ) does not even try to connect to the server. the same url without the "@" works great: http://cal.domain.com/index.php/addressbooks/xxxx-servicename/default/
Additional Information	https://bugzilla.mozilla.org/show_bug.cgi?id=1174527
Tags	No tags attached.

Date Modified	Username	Field	Change
2015-06-14 18:33	evh	New Issue
2015-08-15 15:22	aks42	Note Added: 0008822
2016-07-12 12:05	ludovic	Status	new => assigned
2016-07-12 12:05	ludovic	Assigned To	=> ludovic
2018-03-17 01:16	ludovic	Note Added: 0012776
2018-03-17 01:16	ludovic	Status	assigned => closed
2018-03-17 01:16	ludovic	Resolution	open => suspended
2018-03-17 01:17	ludovic	Relationship added	has duplicate 0002927

aks42 2015-08-15 15:22 reporter ~0008822	I had s similar issue, see 0003280. In my case the solution was to use https instead of http.

ludovic 2018-03-17 01:16 reporter ~0012776	Should work well now since we are use the password management code of Lightning for years now.