an order-of-magnitude optimization which also improves correctness

[git.ikiwiki.info.git] / doc / bugs / trouble_with_base_in_search.mdwn

diff --git a/doc/bugs/trouble_with_base_in_search.mdwn b/doc/bugs/trouble_with_base_in_search.mdwn
index 16e4e74681a7af8e3abb866649480c4149421b5d..ca6a6c5ccfe37e96f92ebe2948584d192cc6e427 100644 (file)
--- a/doc/bugs/trouble_with_base_in_search.mdwn
+++ b/doc/bugs/trouble_with_base_in_search.mdwn
@@ -41,3 +41,20 @@ Here's a patch:
 
 It works for me, but it has the odd side-effect of prefixing links with a space.  Fortunately that doesn't seem to break browsers.
 And I'm sure someone else could come up with something better and more general.
 
 It works for me, but it has the odd side-effect of prefixing links with a space.  Fortunately that doesn't seem to break browsers.
 And I'm sure someone else could come up with something better and more general.

+
+--[[KathrynAndersen]]
+
+> The `<base href>` is required to be genuinely absolute (HTML 4.01 §12.4).
+> Have you tried setting `url` to the public-facing URL, i.e. with `alfred`
+> as the hostname? That seems like the cleanest solution to me; if you're
+> one of the few behind the firewall and you access the site via `betty`
+> directly, my HTTP vs. HTTPS cleanup in recent versions should mean that
+> you rarely get redirected to `alfred`, because most URLs are either
+> relative or "local" (start with '/'). --[[smcv]]
+
+>> I did try setting `url` to the "Alfred" machine, but that doesn't seem clean to me at all, since it forces someone to go to Alfred when they started off on Betty.
+>> Even worse, it prevents me from setting up a test environment on, say, Cassandra, because as soon as one tries to search, one goes to Alfred, then Betty, and not back to Cassandra at all.
+>> Hardcoded solutions make me nervous.
+
+>> I suppose what I would like would be to not need to use a `<base href>` in searching at all.
+>> --[[KathrynAndersen]]