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?

Comments

  1. Mark Dickens18 March 2017 at 09:22

    If I add --http1.1 to the curl command it works fine

    ReplyDelete
  2. Kirill Maximov (KIR)18 March 2017 at 10:19

    Strange, Checkvist should work with HTTP/2 protocol (curl key --http2). We haven't changed anything since January with this regard.

    ReplyDelete
  3. Mark Dickens3 April 2017 at 01:23

    Finally got back to this...

    Auth using
    curl --http1.1 "https://checkvist.com/auth/login.json?username=&remote_key="

    Works but with --http2 I get "curl: (1) Unsupported protocol"

    ReplyDelete
  4. Kirill Maximov (KIR)3 April 2017 at 01:51

    Does your curl fresh enough to support http2? Is there --http2 option in curl --help output?

    ReplyDelete
  5. Mark Dickens3 April 2017 at 03:13

    Hi Kirill Maximov,

    Yes, 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




    ReplyDelete
  6. Kirill Maximov (KIR)3 April 2017 at 03:19

    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

Post a Comment

Popular posts from this blog

Any Toggl users here?

Any Toggl users here? I'm putting together an integration so the toggl (Chrome extension) button ( https://github.com/toggl/toggl-button ) is displayed for tasks on a Checkvist list. It's dead simple (a few lines of javascript), but I'm slightly torn on the best way to handle one aspect: whether or not toggl is shown for a particular list. It can't be always-on, as it adds too much clutter for non-projecty lists (who wants a timer button for the carrots on their grocery list?). What I have now is that if any task on a list is tagged #toggl, then all tasks on that list will have the toggl button. A few alternatives I canvassed were: - display toggl buttons only on subtasks of a task tagged with #toggl - display toggl buttons only on focused (hoisted) tasks - find some other way to indicate that all of a list's tasks should have the button, eg. something encoded in the list's name I think what I have now is the most convenient of these (I don't want to hav...
Read more