diff --git a/doc/bugs/webdav_remote_fails_on_pound_signs.mdwn b/doc/bugs/webdav_remote_fails_on_pound_signs.mdwn
index 88593a8ed4..35455023d3 100644
--- a/doc/bugs/webdav_remote_fails_on_pound_signs.mdwn
+++ b/doc/bugs/webdav_remote_fails_on_pound_signs.mdwn
@@ -57,3 +57,5 @@ It wouldn't be so bad if git-annex would fail to upload to a webdav repo and jus
 ### 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)
 
 I'm running out of ideas here, to be honest. I've certainly had a lot of "luck" running git-annex before, but as others have said, "there's no such thing as luck" and the reason this whole thing works at all is because you work so hard on making it. So: thanks again! --[[anarcat]]
+
+> [[fixed|done]] --[[Joey]]
diff --git a/doc/bugs/webdav_remote_fails_on_pound_signs/comment_2_a88aa0458413481787b4a59990a210df._comment b/doc/bugs/webdav_remote_fails_on_pound_signs/comment_2_a88aa0458413481787b4a59990a210df._comment
index c2dbf1a295..9413e7b5f0 100644
--- a/doc/bugs/webdav_remote_fails_on_pound_signs/comment_2_a88aa0458413481787b4a59990a210df._comment
+++ b/doc/bugs/webdav_remote_fails_on_pound_signs/comment_2_a88aa0458413481787b4a59990a210df._comment
@@ -4,4 +4,9 @@
  date="2019-02-07T17:47:06Z"
  content="""
 Fixed for webdav, still need to check S3.
+
+Update: S3 does not have the problem, because the path to a S3 object is
+also part of the url, and yet S3 doesn't special case '#' and '?'.
+
+Kind of makes me wonder if all webdav servers have the problem either.
 """]]