Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cleanup: Add more documentation and cleanup. #298

Merged
merged 1 commit into from
Dec 1, 2015

Conversation

harshavardhana
Copy link
Member

No description provided.

harshavardhana pushed a commit that referenced this pull request Dec 1, 2015
cleanup: Add more documentation and cleanup.
@harshavardhana harshavardhana merged commit aceaaae into minio:master Dec 1, 2015
@harshavardhana harshavardhana deleted the cleanup-more branch December 1, 2015 06:29
vsoch added a commit to researchapps/minio-py that referenced this pull request Apr 6, 2020
In the case that the user wants to use the minio-py client to generate
a presigned url, also in the case that a server is making a request on
behalf of a command line client (where the object to be uploaded lives)
this means that the command line client will need to send the sha256sum
to the server (which is not able to calculate it). In practice I was
attempting this workflow (singularity/sregistry PR minio#298) and getting
an invalid signature every time. I figured out that the sha256sum was
important because it was being sent to the server from the Singularity
command line tool, and the trick was getting it into the function
preload_v4 so that it would be included in the signature calculation.
Once I was able to do this, my pre-signed urls for multipart upload
worked like a charm! While I think it would be great for minio-py to have
a fully supported function to generate these URLS more easily, in the
meantime this small change to allow specifying the content_hash_hex
will be useful to users that have similar use case to me

Signed-off-by: vsoch <vsochat@stanford.edu>
vsoch added a commit to researchapps/minio-py that referenced this pull request Apr 6, 2020
In the case that the user wants to use the minio-py client to generate
a presigned url, also in the case that a server is making a request on
behalf of a command line client (where the object to be uploaded lives)
this means that the command line client will need to send the sha256sum
to the server (which is not able to calculate it). In practice I was
attempting this workflow (singularity/sregistry PR minio#298) and getting
an invalid signature every time. I figured out that the sha256sum was
important because it was being sent to the server from the Singularity
command line tool, and the trick was getting it into the function
preload_v4 so that it would be included in the signature calculation.
Once I was able to do this, my pre-signed urls for multipart upload
worked like a charm! While I think it would be great for minio-py to have
a fully supported function to generate these URLS more easily, in the
meantime this small change to allow specifying the content_hash_hex
will be useful to users that have similar use case to me

Signed-off-by: vsoch <vsochat@stanford.edu>
vsoch added a commit to researchapps/minio-py that referenced this pull request Apr 7, 2020
In the case that the user wants to use the minio-py client to generate
a presigned url, also in the case that a server is making a request on
behalf of a command line client (where the object to be uploaded lives)
this means that the command line client will need to send the sha256sum
to the server (which is not able to calculate it). In practice I was
attempting this workflow (singularity/sregistry PR minio#298) and getting
an invalid signature every time. I figured out that the sha256sum was
important because it was being sent to the server from the Singularity
command line tool, and the trick was getting it into the function
preload_v4 so that it would be included in the signature calculation.
Once I was able to do this, my pre-signed urls for multipart upload
worked like a charm! While I think it would be great for minio-py to have
a fully supported function to generate these URLS more easily, in the
meantime this small change to allow specifying the content_hash_hex
will be useful to users that have similar use case to me

Signed-off-by: vsoch <vsochat@stanford.edu>
vsoch added a commit to researchapps/minio-py that referenced this pull request Apr 7, 2020
In the case that the user wants to use the minio-py client to generate
a presigned url, also in the case that a server is making a request on
behalf of a command line client (where the object to be uploaded lives)
this means that the command line client will need to send the sha256sum
to the server (which is not able to calculate it). In practice I was
attempting this workflow (singularity/sregistry PR minio#298) and getting
an invalid signature every time. I figured out that the sha256sum was
important because it was being sent to the server from the Singularity
command line tool, and the trick was getting it into the function
preload_v4 so that it would be included in the signature calculation.
Once I was able to do this, my pre-signed urls for multipart upload
worked like a charm! While I think it would be great for minio-py to have
a fully supported function to generate these URLS more easily, in the
meantime this small change to allow specifying the content_hash_hex
will be useful to users that have similar use case to me

Signed-off-by: vsoch <vsochat@stanford.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant