Andrew J. Berkley

Feel free to steal the connection-cache from dexador... https://github.com/fukamachi/dexador/blob/master/src/connection-cache.lisp

I will work on correcting the implementation of this in cl+ssl. Then if I am still happy, will add to dexador and drakma.

I don't know how kerberos + http works so I can't answer your question, but felt that silence isn't a great answer either. My vague understanding is Kerberos authentication would...

You can remove :WINDOWS from `*features* `before loading dexador to have it use the usocket backend by default. I looked through the cookie header generating code for winhttp and didn't...

Are you using connection pooling in dex? The data that is being sent is "POST /v1/service/!..." so this is likely the first thing we are doing on this connection. I...

So if the stream is already closed, we should be getting a closed-stream-error, not this internal error... so it's a bit confusing. The only way to get around that I...

So reusing-stream-p is nil, which means this connection didn't come from the connection pool...

It's maybe something wrong in the maze of auto-retry logic... but I can't see anything wrong. But, like I said, it's a maze.

Is this a "new" problem? (I mean, was it occuring before, but now with say the newest quicklisp it is?)

Unfortunately I don't have much of a lead. What it looks like is you should be seeing the "broken pipe error" which would make it clear what the problem is...