Commit Graph

10 Commits

Author SHA1 Message Date
jrconlin a2dbc6f0f1
chore: tag 1.13.0 2021-03-16 07:51:54 -07:00
JR Conlin 32e3fd9420
bug: Update vapid `exp` value if it's expired. (#113)
Closes #100
2019-05-09 10:05:00 -07:00
jrconlin 110be71459
f update README files 2019-01-04 13:58:32 -08:00
jrconlin 5e8189849b bug: return the remote server response in the WebpushException
Closes #90
2018-03-30 10:42:38 -07:00
jrconlin 1d1e1d47d2 bug: merge fail 2017-12-04 15:31:40 -08:00
David D Lowe d0461a350f Make README.rst acceptable to PyPI's website
When running a check against README.rst, I got these errors:

    warning: check: Cannot analyze code. No Pygments lexer found for "commandline". (line 87)
    warning: check: Cannot analyze code. No Pygments lexer found for "pythonstub". (line 93)

I had previously ignored them, because they were just warnings.

However, according to this link, usage of non-builtin lexers will cause
the RST to not be recognised by PyPI.

https://github.com/twolfson/restructuredtext-lint/tree/0.14.2#pypi-issues
2017-05-11 09:59:40 +01:00
jrconlin 812b8c7110 feat: update to use Cryptography library
* 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
2017-05-10 16:24:03 -07:00
jrconlin caf331dab8 feat: Allow VAPID with [gf]cm
* added primative CLI
* dump as curl

closes #44
2017-03-21 20:21:11 -07:00
Rémy HUBSCHER 754ebb8a64
Update badge repository names. 2017-02-10 14:38:13 +01:00
jrconlin 8ff7c68248 Convert README from markdown to restructured text
closes #35
2017-02-06 16:16:35 -08:00