From 9964d0d4819d358fe9552649504186b4032b4b92 Mon Sep 17 00:00:00 2001
From: Matthew Feickert <matthew.feickert@cern.ch>
Date: Sat, 22 Jun 2019 13:09:16 -0400
Subject: [PATCH] Use curl -L to have trigger_binder follow URL redirect (#17)

BinderHub now operates as a Binder Federation and so there is no
guarantee where the Binder build will take place. As a result, the
Binder trigger must follow any redirect of the URL.

c.f.
https://discourse.jupyter.org/t/problem-triggering-binder-build-through-api-endpoint/1440
---
 binder/trigger_binder.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/binder/trigger_binder.sh b/binder/trigger_binder.sh
index 90bca45..2e0c9af 100644
--- a/binder/trigger_binder.sh
+++ b/binder/trigger_binder.sh
@@ -3,7 +3,7 @@
 function trigger_binder() {
     local URL="${1}"
 
-    curl --connect-timeout 10 --max-time 30 "${URL}"
+    curl -L --connect-timeout 10 --max-time 30 "${URL}"
     curl_return=$?
 
     # Return code 28 is when the --max-time is reached