* Support adding arbitrary HTTP headers when using webpush()
Useful for adding headers like `Topic` an `Urgency` that don't have
dedicated parameters.
* Send headers provided in the `--head` CLI argument
In Python 2, using six.string_types causes the code to attempt to re-encode already encoded data because six.string_types matches Python 2 str and unicode data. Using six.text_type makes sure that the code only attempts to encode unicode data.
Altering subscriptions reference by changing the keys from string to
byte causes hard to debug issues in libraries. For exemple, trying to
call `json.dumps()` after initializing `WebPusher` throws an error
because json cannot handle bytes.
* uses lastest ece(1.7.2) and vapid libraries (1.2.1)
* Will attempt to autofill vapid `aud` from the endpoint if VAPID
requested
* Allows for the older `'aesgcm'` and newer, albeit not as widely
supported `'aes128gcm'` encryption content types.
* Includes fixes provided by https://github.com/Flimm
NOTE: Currently BLOCKED due to
https://github.com/martinthomson/encrypted-content-encoding/issues/36
closes: #49, #48, #42
use new "content_type" argument to specify either "aesgcm" (draft-01)
or "aes128gcm" (draft-04).
NOTE: Not all clients yet support Draft-04.
closes #33
Updated libraries and tests for latest depenedent library versions.
Note: can't tie in requires.io quite yet, investigating how to best do
that.
fixes: #18
Updated libraries and tests for latest depenedent library versions.
Note: can't tie in requires.io quite yet, investigating how to best do
that.
fixes: #18
FCM, unfortunately, rejects multiple parameter sets for Crypto-Key.
This is a work-around fix until the issue is properly resolved by the
respective working groups.
closes #8
FCM, unfortunately, rejects multiple parameter sets for Crypto-Key.
This is a work-around fix until the issue is properly resolved by the
respective working groups.
closes #8