Updating all commits from forked branch #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
startByte and byteCount variables are explicitly casted to neutral form to avoid incompatibility in uint64_t format string across platforms.
… script to reflect failures
…n/signature logic
Empty header is not sent by curl, but gets included to the list of signed headers and breaks authorization for minio. And probably for other server implementations too.
Empty header is not sent by curl, but gets included to the list of signed headers and breaks authorization for minio. And probably for other server implementations too.
Fix OSX build error due to uint64_t format string incompatibility
Support older libcurl versions
Improve test script
Fix minio compatibility. Do not append empty Transfer-Encoding header.
Upgrade Authentication to use AWS Signature Version 4
fix S3_destroy_request_context() to correctly abort curl_multi context
from "Like Ma" (likema on github).
Fix building error in Ubuntu 12.04
Fix strip error when cross compiling.
Fix urlencode error according to AWS S3 documents.
create bucket: ignore response body
Fix crash in Windows by init and deinit libxml2 parser.
# Conflicts: # src/request.c
Make libs3 work with curl_multi_socket_action mode where libs3 user will drive socket polling instructed directly by curl through a set of callbacks. This is an addition to the curl_multi_perform mode where libs3 does the polling itself.
Signed-off-by: yuliyang <[email protected]>
Following AWS S3's increased single-object size limit, allow the upload of data > 5 GB
This fixes the following error encountered when uploading large files: ERROR: ErrorMalformedXML Message: The XML you provided was not well-formed or did not validate against our published schema. This becomes a problem after a previous patch increases the size limit for a single object, causing more than one growbuffer to be allocated for holding the XML.
Fixes "segfault while putting large files read from stdin"
extension to support curl_multi_socket_action operation
add bucket-owner-full-control for x-amz-acl
Increasing the chunk size avoids an issue where too many parts are uploaded, triggering an error when calling the S3 CompleteMultipartUpload API command. The current limit on the number of parts per upload is 10,000 according to the S3 documentation (https://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html)
S3_initiate_multipar will save param callbackData in struct InitialMultipartData, and passed InitialMultipartData* as callback data to S3PropertiesCallback, which make a crash when extract user defined data from S3PropertiesCallback
is licensed under LGPLv3 *or above* or GPLv2 *or above* (user's choice).
libs3 fails to build with 7.62 currently:
src/request.c: In function 'request_curl_code_to_status':
src/request.c:1703:5: error: duplicate case value
case CURLE_SSL_CACERT:
src/request.c:1699:5: note: previously used here
case CURLE_PEER_FAILED_VERIFICATION:
… were not buffer overflow safe.
build: support curl >= 7.62
fix bug on S3_initiate_multipart
tok is set NULL in strtok_r loop, so free was called for NULL, instead of the original pointer
Memory leak
Fix uploading large amounts of data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.