https://bugzilla.wikimedia.org/show_bug.cgi?id=31369
--- Comment #25 from Krinkle <[email protected]> 2012-06-28 02:21:59 UTC --- (In reply to comment #24) > (In reply to comment #23) > > Actually there is dozens and dozens more: > > > > https://gerrit.wikimedia.org/r/gitweb?p=operations/apache-config.git;a=blob;f=redirects.conf;h=a777adf9dfb5f8652289c7855b06e5be43767a9b;hb=HEAD#l176 > > Right. The question is whether these can be solved in a simpler/cleaner/saner > way than specifying "RewriteCond %{HTTPS} off" and "RewriteCond %{HTTPS} on" a > million times. > > According to my reading of > <http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30>, the > Location > header must be an absolute URI. Someone suggested that switching these rules > to > use protocol-relative syntax might resolve this bug, but in addition to the > HTTP spec, Apache's rewrite/redirect logic apparently interprets any string > beginning with a "/" to be a relative URI path, so that option is a no-go. > Indeed. The spec says it should be absolute and apache doesn't support relative. But, browsers (the ones I've tested) do and always have supported relative Location headers. But anyway, as you say, a no-go. > As I said earlier, %{HTTPS} might be best... but it's going to result in an > awful lot of code duplication for one letter. We could go for a build process. Where the thing is auto-generated adding one for each with the HTTPS case. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
