Open Bug 959035 Opened 11 years ago Updated 2 years ago

Don't send X-Confirm-Delete header to sync1.5 storage servers

Categories

(Firefox :: Sync, defect, P5)

defect

Tracking

()

People

(Reporter: rfkelly, Unassigned)

References

Details

(Whiteboard: [qa?])

Per the proposed sync1.5 protocol docs in Bug 951986, the sync storage servers will no longer require an "X-Confirm-Delete" header on delete requests.  Desktop sync client should avoid sending this header if it knows it's talking to a sync1.5 server.

Note that it's safe to send the header anyway if you need to, as it will be ignored.
Whiteboard: [qa?]
N.B., given that the backend client code is shared, this removal either needs to be conditional or to only occur when Sync 1.1 is deprecated.
I'm tempted to just WONTFIX this as it's such a tiny bug, but maybe we can move on it now that sync1.1 has been end-of-lifed?  We don't have an official policy on maintaining compatibility in client code, although in [1] I back-handedly suggest that we won't begin breaking it until 2016.

[1] https://blog.mozilla.org/services/2015/07/31/shutting-down-the-legacy-sync-service/
(In reply to Ryan Kelly [:rfkelly] from comment #2)
> I'm tempted to just WONTFIX this as it's such a tiny bug, but maybe we can
> move on it now that sync1.1 has been end-of-lifed?  We don't have an
> official policy on maintaining compatibility in client code, although in [1]
> I back-handedly suggest that we won't begin breaking it until 2016.

self-hosters remain a problem, so I don't think we can do it now. I don't see a problem keeping it open and fixing it some time next year though :)
Flags: firefox-backlog+
Priority: -- → P3
No longer blocks: 905997
Priority: P3 → P5
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.