followup

doc/bugs/suggests_to_enable_web_remote_even_when_there_is_no_web_urls_for_the_file/comment_1_fd32c6a7e5ac6b0ac721dd9edd824c29._comment

@@ -0,0 +1,28 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2018-08-21T15:38:51Z"
+ content="""
+Note that git-annex get from the web remote in this sitation says
+"no known url" before the message you quoted.
+
+Since location tracking and urls are separate peices of information, it's
+certianly possible for them to be inconsistent like this.
+
+It doesn't normally happen though. Eg, `git annex rmurl` of the last url
+of a remote will update location tracking to say it's missing.
+(Special remote SETURLMISSING does the same thing.)
+
+One way it can happen is using `git-annex setpresentkey` 
+to say a key is present in the web, and not setting an url.
+But that's plumbing and it's up the user to use it consistently.
+
+If you have some other way to get into this state that doesn't involve
+plumbing commands, that could be a bug.
+
+It might be possible to add something linking the data so that
+location tracking for the web is ignored if it doesn't have urls, which
+would also need to apply to some other special remotes that use urls, but
+not others that only might have an associated url. I'm doubtful of this
+idea tho.
+"""]]