Justin Karneges

Hi! This is merged: https://github.com/fastly/pushpin/pull/47762

Thanks for your message. It is not possible to log the connection ID, but this could be a reasonable feature to add.

Hi Peter, Are you seeing the "inspect not available" message for incoming client requests too, or only for next link fetches?

I was able to reproduce this. It seems the issue has to do with external routing (when the scheme/domain of the next link is different than that of the original...

Interesting, I didn't realize anyone was doing WebSockets over HTTP/2 yet. Will digest this. Thank you.

BTW, the check has now been relaxed to allow `Content-Length: 0`, for compatibility with Java, which partly helps with this issue too. The `Sec-WebSocket-Key` header is still required though.

The general memory usage issue has been fixed in 839919251e6e042cecaa415d5968329baeeb291c, which means changing `HEADERS_MAX` now has only modest effect on memory usage. I've gone ahead and increased it to 64...

I don't think we'd want to allow an arbitrary number of headers, as one of the design goals of condure is to ensure the amount of memory per-connection is predictable....

Hi there. The project uses django-dotenv, which is different from python-dotenv. Be sure to install all the dependencies from requirements.txt.

We're no longer including such compiled files in the repo. You can build like this: ``` sh npm install . npm run build ``` @harmony7: probably the readme should be...