X-Last-Modified header missing from /info/configuration response in v0.5.3 #759
Assignees
Comments
jrconlin
added
5
pjenvey
added a commit
that referenced
this issue
Aug 4, 2020
pjenvey
added a commit
that referenced
this issue
Aug 4, 2020
jrconlin
added a commit
that referenced
this issue
Aug 6, 2020
Closes #759 Co-authored-by: JR Conlin <[email protected]> Co-authored-by: jrconlin <[email protected]>
|
Thanks folks! If possible, could you please comment here or in mozilla/application-services#3379 once this is deployed to stage, so that we can unlock QA of the mobile clients? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a spinoff from the discussion over in mozilla/application-services#3379.
On version 0.4.2 of syncstorage-rs (currently in production) the server includes an
X-Last-Modifiedheader in its response to the/info/configurationrequest. It's honestly kind of weird to include it on this particular request, because it's not really a part of the stored data that can be modified. But be that as it may, the api docs do say that this header "will be included in all success responses", and the Rust sync client code will error out if it is missing from any response.On version 0.5.3 of syncstorage-rs (currently in stage) the server no longer seems to include an
X-Last-Modifiedheader in the response to this request. I'm not sure what changed, and it may only occur for new accounts, but it's currently preventing QA from testing syncing on stage, ref mozilla/application-services#3379 and mozilla-services/syncserver#221.Could we please restore the
X-Last-Modifiedheader on all success responses?The text was updated successfully, but these errors were encountered: