mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #626] no_check_certificate seems to have no effect #360
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#360
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?
Originally created by @djdevin on GitHub (Jul 28, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/626
We have a domain bucket in us-east-1.
Amazon's S3 wildcard only covers *.s3.amazonaws.com
Setting no_check_certificate seems to have no effect, the SSL is still rejected.
We can't use s3.amazonaws.com as the endpoint because it tells us "The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint."
@ggtakec commented on GitHub (Sep 17, 2017):
@djdevin Does your bucket name include "."?
If so, you must specify the use_path_request_style option.
Please let me know if it is wrong.
Thanks in advance for your assistance.
@djdevin commented on GitHub (Nov 6, 2017):
It does, but it still does not appear to work. It seems impossible to mount a bucket with periods in the name. Same as #653
The 301's are returning this: "The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint."
The endpoint should be "endpoint=backup.bucket.example.com.s3.amazonaws.com"
But if you change to that endpoint, you get:
Even if "no_check_certificate" is set.
@ggtakec commented on GitHub (Mar 29, 2019):
We kept this issue open for a long time.
Please try again with the latest version and you can see https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-https-connecting-failed-if-bucket-name-includes-dot- .
I will close this, but if the problem persists, please reopen or post a new issue.