Closed Bug 736374 Opened 9 years ago Closed 2 years ago

Protocol 2.0: send X-If-Modified-Since and handle 304 when info/collections and meta/global are unchanged

Categories

(Cloud Services :: Server: Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rnewman, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [qa+])

See Bug 736370.
Whiteboard: [qa+]
Blocks: 744320
I've proposed this (and an extension) in the FxA+token world to avoid some excess work in the client. Further discussions ongoing.
Blocks: 960878
Priority: -- → P2
Priority: P2 → --
This would require support from the server, then a client bug could be opened to actually leverage it, so I'm changing the component to get it out of our desktop triage list.
Component: Firefox Sync: Backend → Server: Sync
The server appears to have support and tests for X-If-Modified-Since and a 304 on /info/collections, so I'm closing this server bug.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Summary: Protocol 2.0: send X-If-Unmodified-Since and handle 304 when info/collections and meta/global are unchanged → Protocol 2.0: send X-If-Modified-Since and handle 304 when info/collections and meta/global are unchanged
You need to log in before you can comment on or make changes to this bug.