Skip to content
This repository was archived by the owner on Feb 12, 2023. It is now read-only.

Issue 409 remove Location header from 204 HTTP responses #417

Merged
merged 3 commits into from
Mar 5, 2019
Merged

Issue 409 remove Location header from 204 HTTP responses #417

merged 3 commits into from
Mar 5, 2019

Conversation

ggalmazor
Copy link
Contributor

Closes #409

What has been done to verify that this works as intended?

Verify in Aggregate:

  • Uploading forms works
  • Manually uploading a submission works
  • Changing user password and granted permissions works

Verify using Briefcase:

  • Pushing a form with submissions works

Why is this the best possible solution? Were any other approaches considered?

HTTP 204 responses should not have a Location header.

Are there any risks to merging this code? If so, what are they?

Nope.

Do we need any specific form for testing your changes? If so, please attach one

No.

Does this change require updates to documentation? If so, please file an issue at https://github.com/opendatakit/docs/issues/new and include the link below.

No.

@ggalmazor ggalmazor added this to the v2.0.1 milestone Feb 12, 2019
@ggalmazor ggalmazor changed the title Issue 409 ensure location header is only used in 201 and 3xx responses Issue 409 remove Location header from 204 HTTP responses Feb 12, 2019
@kkrawczyk123
Copy link

Tested with success!
I've checked points mentioned in the pr, I haven't noticed anything suspicious.

@opendatakit-bot unlabel "needs testing"
@opendatakit-bot label "behavior verified"

@ggalmazor ggalmazor merged commit ad621fa into getodk:master Mar 5, 2019
@ggalmazor ggalmazor deleted the issue_409_ensure_Location_header_is_only_used_in_201_and_3xx_responses branch March 5, 2019 14:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants