Something's changed?
Something's changed?
I have a curl script which was allowing me to add tasks to Checkvist really easily.
The script (unchanged) is now erroring:
curl: (92) HTTP/2 stream 1 was not closed cleanly: REFUSED_STREAM (err 7)
Any ideas anyone?
I have a curl script which was allowing me to add tasks to Checkvist really easily.
The script (unchanged) is now erroring:
curl: (92) HTTP/2 stream 1 was not closed cleanly: REFUSED_STREAM (err 7)
Any ideas anyone?
If I add --http1.1 to the curl command it works fine
ReplyDeleteStrange, Checkvist should work with HTTP/2 protocol (curl key --http2). We haven't changed anything since January with this regard.
ReplyDeleteFinally got back to this...
ReplyDeleteAuth using
curl --http1.1 "https://checkvist.com/auth/login.json?username=&remote_key="
Works but with --http2 I get "curl: (1) Unsupported protocol"
Does your curl fresh enough to support http2? Is there --http2 option in curl --help output?
ReplyDeleteHi Kirill Maximov,
ReplyDeleteYes, the version of curl I am using supports http2:
-0, --http1.0 Use HTTP 1.0 (H)
--http1.1 Use HTTP 1.1 (H)
--http2 Use HTTP 2 (H)
--http2-prior-knowledge Use HTTP 2 without HTTP/1.1 Upgrade (H)
--ignore-content-length Ignore the HTTP Content-Length header
I'm using curl in conjunction with autohotkey and I'm happy to use http1.1 but the scripting has started to fail (the auth request returns the auth key but autohotkey has started to fail to read the output.
This is a me problem not a checkvist problem :) )
Just not sure why curl --http2 fails but curl --http1.1 works
I believe this is the explanation, the curl is broken a bit: simonecarletti.com - Using cURL with HTTP/2 on Mac OS X — Simone Carletti
ReplyDelete