From 5a7b3955595b83fa266428885ababb446fb83b65 Mon Sep 17 00:00:00 2001
From: Dominic Brekau <35068626+dbrekau@users.noreply.github.com>
Date: Fri, 9 Mar 2018 14:05:44 +0100
Subject: [PATCH] Update alexa_remote_control.sh

I'm having login problems since 4(?) days, forcing curl to use http1.1 solves this problem.

This is verbose output of curl when using http2:
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
* We are completely uploaded and fine
{ [5 bytes data]
* HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
* Curl_http_done: called premature == 1
* Closing connection 0

In my view this is related to the submitted Referer. But don't know how to fix this at the moment.
---
 alexa_remote_control.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/alexa_remote_control.sh b/alexa_remote_control.sh
index 95e70c0..ab18d3a 100644
--- a/alexa_remote_control.sh
+++ b/alexa_remote_control.sh
@@ -26,6 +26,7 @@
 # 2018-02-27: v0.8e added "lastalexa" option for HA-Bridge to send its command to a specific device
 #		(Markus Wennesheimer: https://wennez.wordpress.com/light-on-with-alexa-for-each-room/)
 # 2018-02-27: v0.9 unsuccessful logins will now give a short info how to debug the login
+# 2018-03-09: v0.9a workaround for login problem, force curl to use http1.1
 #
 ###
 #
@@ -54,7 +55,7 @@ CURL='/usr/bin/curl'
 # cURL options
 #  -k : if your cURL cannot verify CA certificates, you'll have to trust any
 #  --compressed : if your cURL was compiled with libz you may use compression
-OPTS='--compressed'
+OPTS='--compressed --http1.1'
 #OPTS='-k --compressed'
 
 # browser identity