Closed Bug 802601 Opened 12 years ago Closed 12 years ago

Sync fails consistently with 401 on info/collections

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: olivier.vit, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Build ID: 20120905151427 Steps to reproduce: I run FF release channel with multiple profiles on the same computer and sync Passwords only through Mozilla Sync. On one profile, I get very very often a Sync error message at the bottom of the browser window, saying my password is incorrect, however this is the same one as what I have on other profiles. Actual results: request : https://scl2-sync855.services.mozilla.com/1.1/olaparent/info/collections First request: (Request-Line) GET /1.1/olaparent/info/collections HTTP/1.1 Host scl2-sync855.services.mozilla.com User-Agent Firefox/15.0.1 FxSync/1.17.0.20120905151427.desktop Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language en-us,en;q=0.8,fr;q=0.5,fr-fr;q=0.3 Accept-Encoding gzip, deflate Connection keep-alive Authorization Basic b2xhcGFyZW50OmM1Q2hhcmxlcyE= Cookie s_vsn_mozillaservicesmozcom_1=455423164708 no response but second request: (Request-Line) GET /1.1/olaparent/info/collections HTTP/1.1 Host scl2-sync855.services.mozilla.com User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language en-us,en;q=0.8,fr;q=0.5,fr-fr;q=0.3 Accept-Encoding gzip, deflate Connection keep-alive Cookie s_vsn_mozillaservicesmozcom_1=455423164708 Pragma no-cache Cache-Control no-cache Response (Status-Line) HTTP/1.1 401 Unauthorized WWW-Authenticate Basic realm="Sync" Content-Type text/html Strict-Transport-Security max-age=2419200 Date Wed, 17 Oct 2012 13:21:51 GMT Connection keep-alive Content-Length 358 Followed by a request to https://auth.services.mozilla.com/user/1.0/olaparent/node/weave (Status-Line) HTTP/1.1 200 OK Content-Type text/plain; charset=UTF-8 Strict-Transport-Security max-age=2419200 Date Wed, 17 Oct 2012 14:16:45 GMT Connection keep-alive X-Weave-Timestamp 1350483405.41 Content-Length 42 Expected results: Authentication should have worked That profile has pretty few addons compared to other ones Any clue on how to fix this ? (removing the "device" from Sync and adding it again didn't solve the issue)
This is likely bug 798430. Can you download Firefox Nightly from https://nightly.mozilla.org/ and let us know if that fixes it?
Status: UNCONFIRMED → NEW
Depends on: 798430
Ever confirmed: true
Flags: needinfo?(olivier.vit)
Thanks for your attention to this Did you notice that this happens only on one profile, but the same binaries run OK on other profiles ? Couldn't something be done at the profile level to restore normal behavior ? I'll try the nightly anyway
Flags: needinfo?(olivier.vit)
(In reply to Olivier Vit (just a reporter) from comment #2) > Thanks for your attention to this > Did you notice that this happens only on one profile, but the same binaries > run OK on other profiles ? There are lots of code problems that will only be exposed in some profiles. In this case, you might have an add-on that inserts itself into the HTTP request layer, or a cache or proxy configuration that's different, or a PAC file set. > Couldn't something be done at the profile level to restore normal behavior ? It's possible, but (a) we don't know what, and (b) we don't view asking our users to reconfigure their software as a valid solution. > I'll try the nightly anyway Thanks!
Is this working now in Firefox 17, Olivier?
Flags: needinfo?(olivier.vit)
I eventually trashed this profile and created a new one and it's OK Sorry but I didn't test with the nightly. My best
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(olivier.vit)
Resolution: --- → WORKSFORME
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.