Martijn Dwars

I ran into this as well. Gradle's shadow JAR plugin is used by a lot of projects, and after upgrading to the latest version of shadow JAR I still got...

Agreed, thanks for the quick reply.

I just ran into this as well. I'm in a corporate environment and outgoing traffic needs to go through an HTTP proxy. Most tools pick up `HTTP_PROXY`/`HTTPS_PROXY`, Java has its...

You're right, I wonder why this NPE did not pop up earlier. Were you actually confronted with an NPE? Note that the HttpEce standard and WebPush standard are two separate...

First, let me get back at the NPE. The HttpEce implementation is based on [draft-ietf-httpbis-encryption-encoding-02](https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.2), but as you can see the optional `context` string has been dropped since [draft-ietf-httpbis-encryption-encoding-04](https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-ietf-httpbis-encryption-encoding-04.txt). Modern...

Thanks for the feedback. I agree that it's not very clear from the README. Would you be willing to improve the text and create a PR? If not, I will...

> As far as I can currently tell, the public and private key ALWAYS need to be added to the push message, while the code suggests that this is optional,...

I'm sorry, no progress here yet. When I know more, I'll leave a comment on the issue.

Both `userPublicKey` and `userAuth` are generated by the browser. More details can be found in the [specification](https://www.w3.org/TR/push-api/). Specifically, `userPublicKey` and `userAuth` correspond to the following two keys: > - Generate...

> Also please confirm that the PushService's default constructor is to be used with non-chrome browsers (Firefox at the moment.). Seem to be the case but I'd prefer to confirm...