mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-25 13:45:52 +03:00
[PR #1042] [MERGED] supportsuccess_action_status form field for HTML form uploads #1138
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#1138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/fsouza/fake-gcs-server/pull/1042
Author: @vincentezw
Created: 1/11/2023
Status: ✅ Merged
Merged: 1/12/2023
Merged by: @fsouza
Base:
main← Head:main📝 Commits (3)
c16e90acheck for success_action_status form fieldaedb2aereturn xml on 201, PR feedback958810dstruct instead of interface📊 Changes
3 files changed (+62 additions, -5 deletions)
View changed files
📝
fakestorage/upload.go(+18 -1)📝
fakestorage/upload_test.go(+11 -3)📝
fakestorage/xml_response.go(+33 -1)📄 Description
When uploading an object with a HTML form, the GCS XML api allows us to set a
success_action_status: Upload an object with a HTML formPresently
fake-gcs-serverignores this and responds with the default status code 204 (https://github.com/fsouza/fake-gcs-server/blob/main/fakestorage/upload.go#L162)This PR allows us to specify a preferred return value of 200, 201 or 204.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.