From 2cf3d68fe084c03716075e8b57cb1ad612d23736 Mon Sep 17 00:00:00 2001 From: crest Date: Thu, 7 Mar 2019 10:48:01 +0000 Subject: [PATCH] --- ...ecial_remote_limits_HTTPS_support_to_port_443.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/The_S3_special_remote_limits_HTTPS_support_to_port_443.mdwn diff --git a/doc/bugs/The_S3_special_remote_limits_HTTPS_support_to_port_443.mdwn b/doc/bugs/The_S3_special_remote_limits_HTTPS_support_to_port_443.mdwn new file mode 100644 index 0000000000..3fc93c0960 --- /dev/null +++ b/doc/bugs/The_S3_special_remote_limits_HTTPS_support_to_port_443.mdwn @@ -0,0 +1,11 @@ +### Please describe the problem. +The S3 special remote assumes that yout want to use HTTPS iff your service runs on port 443. This isn't true for most minio deployments. + +### What steps will reproduce the problem? +Attempt to add a S3 service using HTTPS and a port != 443 as special remote. + +### What version of git-annex are you using? On what operating system? +Version 7.20181121 on MacOS and 7.20190130-g024120065 on FreeBSD + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) +Yes. I only encountered the problem because git-annex works well enough for me that I want to put a lot more data into it.