Closed
Bug 293456
Opened 20 years ago
Closed 15 years ago
Sunbird asks twice for proxy password
Categories
(Calendar :: Provider: ICS/WebDAV, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jaapf2, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20050203 Mozilla Sunbird/0.2 I have two calendars on a WebDav site. Two access those calendars I first have to give my proxy ID and password, it is filled in by Sunbird. After that I have to give the ID and password for the WebDav site. After that Sunbird asks again for the proxy ID and password, but now nothing is filled in by Sunbird. I don't think Sunbird has to ask twice for the proxy ID and password Reproducible: Always Steps to Reproduce: 1. Start Sunbird (with two calendars on a WebDav site) 2. Sunbird asks for proxy ID and password, already filled in by Sunbird 3. Sunbird asks for WebDav site ID and password, already filled in by Sunbird 4. Sunbird asks again for proxy ID and password, nothing filled in by Sunbird Actual Results: Step 4 accurs after step 4 Expected Results: I don't expect Sunbird to ask the second time for de proxy ID and password. The proxy server I use is a Microsoft one and uses NT credentials.
Comment 1•18 years ago
|
||
dup of bug 248903?
Updated•18 years ago
|
Assignee: shaver → nobody
Component: Internal Components → Provider: ICS/Webdav
QA Contact: base → ics-provider
Comment 2•18 years ago
|
||
I've the same problem with 5 webdav calendars... I must confirm 5 times my proxy login/password and once the webdav server login/password when connecting through the firewall. When connecting from home (no firewall between the PC and the webdav server) I must confirm 5 times the wewdav login/pasword I met this problem after the upgrade to sunbird 0.3 (regression from 0.3a1) on Windows and Linux (french versions)
Comment 3•17 years ago
|
||
Similar Bug 343721 was fixed some time ago. Jaap, Patrick: Does the issue still exists using a recent nightly test build of Sunbird 0.7pre? <http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-mozilla1.8/>
| Reporter | ||
Comment 4•17 years ago
|
||
I'm afraid it still exists. I have two calendars on one site and Sunbird asks twice for my proxy password. When I have one calendar, Sunbird asks once for my password. It should never ask for a password, I clicked on the "use password manager to remember this password". Version is: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7pre) Gecko/20070909 Calendar/0.7pre
Comment 5•17 years ago
|
||
I cannot confirm this with my authenticated proxy. Does your proxy use the same realm as your webdav store or similar? Does this still happen with 0.9pre? A tcp dump of the traffic (passwords removed) might be helpful to see what the MS server is requesting. Please separate this issue from bug 248903. That bug is about asking the password for every calendar, while this one is about asking for the proxy password twice.
Comment 6•16 years ago
|
||
Jaap, can you still confirm this issue with a recent 0.9pre nightly build?
| Reporter | ||
Comment 7•16 years ago
|
||
I'm sorry, I cannot test the last build. I have another job where I'm not allowed to use self installed software.
Comment 8•16 years ago
|
||
Does the issue still exists using Sunbird 0.9 or Sunbird 1.0pre?
Comment 9•15 years ago
|
||
No response for a while now, closing INCOMPLETE. Please reopen if you can reproduce or answer any unanswered questions.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Comment 10•14 years ago
|
||
I am experiencing similar behavior. In addition to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=349641">Bug 349641</a>, I get repeated requests for my proxy password when retrieving remote calendars. Using GoogleProvider 0.6b1, Lighting 1.0b1, going through Squid Proxy.
Comment 11•14 years ago
|
||
UPDATE: Recent update to GoogleProvider 0.7 and Lightning 1.0b2 seems to have fixed the problem.
You need to log in
before you can comment on or make changes to this bug.
Description
•