Kumar McMillan

Before pip changed, a patch was in the works here https://github.com/erikrose/peep/pull/61

The port gets connected [here](https://github.com/kumar303/default-opener/blob/master/extension/background.js#L1) so I would check earlier in the log to see if there's a reason for why it got disconnected. As I understand it, Chrome starts...

actually, heh, you probably won't see any logging. I just added it so pull in these git changes and reload the extension (or restart Chrome). https://github.com/kumar303/default-opener/commit/d33d1135f67687da54e7f1ed8eb8a245bbe1c529

Well, huh. It looks like `mohawk` defers to how [`urlparse()`](https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlparse) gives us the port when parsing the URL. I'm not sure what the best thing to do here is. You...

> My current workaround is to fork mohawk and force port 433 for all url schemes. It would be nicer if you could specify a port when creating a receiver...

Yes, `Receiver(..., defer_content_hash=True)` sounds good. As for `check_hash()`, this should probably be designed with large payloads in mind, right? As I recall, that's the main use case here. My Python...

I think a low level interface with `set_content_type()`, `add_content()`, and `verify_content()` directly on Receiver might be a bit awkward because you have to remember to call `verify_content()` at the end....

I think it would be good to start with a context manager and see where we end up. I am having trouble imagining a situation where you *could not* use...

Hi. Thanks for taking time to file an issue. This message is warning you that that the *request* did not contain a nonce and that your receiver is not configured...

Thanks for the code sample. I haven't tried to run this but I think it's because your `Sender` is not configured for nonce checking. When you run `sender.accept_response()`, the sender...