RaspberryPi/alexa-remote-control
1
0
Fork 0
mirror of https://github.com/thorsten-gehrig/alexa-remote-control.git synced 2024-11-22 08:49:02 +01:00
Code Issues Releases Wiki Activity

Update alexa_remote_control.sh

Browse Source 
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.
This commit is contained in:
Dominic Brekau 2018-03-09 14:05:44 +01:00 committed by GitHub
parent 6076978f9a
commit 5a7b395559
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
alexa_remote_control.sh
View File

@ -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