You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, this specific example (with the leading /), is not valid when used with the fog-aws backend. Some S3 providers will tolerate it (AWS S3 allows it via API, but not via their web console). Some providers will not allow it at all (minio rejects object names with a leading slash).
I haven't been able to track down docs that give me enough clarity on how cache_dir should be used to offer a PR, but it seems like this is a good candidate for improved docs, and ideally throwing an exception in the case where fog_aws is in use and an improper cache_dir has been specified. It took quite a bit of troubleshooting to figure this out and I'd like to save the next person the trouble. Thanks.
The text was updated successfully, but these errors were encountered:
Apologies this isn't a PR to improve the docs, but I've dug quite a bit and am not sure what the right answer is.
In
README.md
the example usage for cache_dir is:However, this specific example (with the leading /), is not valid when used with the
fog-aws
backend. Some S3 providers will tolerate it (AWS S3 allows it via API, but not via their web console). Some providers will not allow it at all (minio rejects object names with a leading slash).I haven't been able to track down docs that give me enough clarity on how cache_dir should be used to offer a PR, but it seems like this is a good candidate for improved docs, and ideally throwing an exception in the case where
fog_aws
is in use and an improper cache_dir has been specified. It took quite a bit of troubleshooting to figure this out and I'd like to save the next person the trouble. Thanks.The text was updated successfully, but these errors were encountered: