-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
how to generate share url permanent? #5180
Comments
@timchenxiaoyu Presigned URLs are valid only for a maximum of 7 days. This is mandated by S3 Spec (Ref: http:https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html). For permanent sharing you can consider buckets policies - https://docs.minio.io/docs/minio-client-complete-guide#policy |
Please lets us know if you have any other questions. |
even I set buckets policies, I cannot still get permanent url,how to solve this? |
Once you set the policy on a bucket like
You can use the URL: |
#mc policy public minio/test Access permission for #wget http:https://10.39.0.45:9000/test/types-of-mounts.png it's ok now .ths. |
You need to remove
|
yes, you are right ,ths |
@nitisht
This gives a signature of S3 and Minio accepts this signature and display the object Why does it work? |
This is a presigned URL but it is not permanent @FoxUSA |
@harshavardhana Signature
Epoch time sets that signature to expire in the year 2739925. |
Yes only in AWS Signature v2 (legacy), AWS Signature v4 has limited it to maximum of 7 days. |
It would be good if somebody point out in docs that polycy prefix should not start with slash / when you type it in via web intrerface, got fooled by that slash hard before checked policies via mc. |
UI is being revamped you won't be allowed to type incorrect values. |
how should i do this via sdk(js)?
|
@woodgear Here is the policy
Replace |
All I did create a new location in nginx something like /bucketname and in the block add root to the local path for the bucket folder. |
now ,the url only 7 minute valid,how to change this?
The text was updated successfully, but these errors were encountered: