From 2c9a2ae285b0806a5f754dcf6064f7cedc7e1fa8 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Wed, 31 May 2017 01:18:04 -0400 Subject: docs/config: mention protocol implications of url.insteadOf If a URL rewrite switches the protocol to something nonstandard (like "persistent-https" for "https"), the user may be bitten by the fact that the default protocol restrictions are different between the two. Let's drop a note in insteadOf that points the user in the right direction. It would be nice if we could make this work out of the box, but we can't without knowing the security implications of the user's rewrite. Only the documentation for a particular remote helper can advise one way or the other. Since we do include the persistent-https helper in contrib/ (and since it was the helper in the real-world case that inspired that patch), let's also drop a note there. Suggested-by: Elliott Cable Signed-off-by: Jeff King Signed-off-by: Junio C Hamano --- contrib/persistent-https/README | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'contrib') diff --git a/contrib/persistent-https/README b/contrib/persistent-https/README index f784dd2e66b..7c4cd8d257d 100644 --- a/contrib/persistent-https/README +++ b/contrib/persistent-https/README @@ -35,6 +35,16 @@ to use persistent-https: [url "persistent-http"] insteadof = http +You may also want to allow the use of the persistent-https helper for +submodule URLs (since any https URLs pointing to submodules will be +rewritten, and Git's out-of-the-box defaults forbid submodules from +using unknown remote helpers): + +[protocol "persistent-https"] + allow = always +[protocol "persistent-http"] + allow = always + ##################################################################### # BUILDING FROM SOURCE -- cgit v1.2.3