An open API service for providing issue and pull request metadata for open source projects.

GitHub / pimeys/rust-web-push issues and pull requests

#73 - assertion `left == right` failed

Issue - State: open - Opened by a-kolechko 3 months ago - 1 comment

#72 - Add declarative Notification payload builder

Pull Request - State: open - Opened by danieldickison 4 months ago

#71 - `0.10.2` → `0.10.3` updates include a breaking change

Issue - State: closed - Opened by naskya 5 months ago - 1 comment

#70 - Remove padding = from openssl base64 public key

Pull Request - State: closed - Opened by ducklol2 6 months ago

#69 - Fix private_key filename in README.md

Pull Request - State: closed - Opened by ducklol2 6 months ago

#68 - Limit push endpoint response size

Pull Request - State: closed - Opened by niklasf 8 months ago

#67 - Bump deps (simple part only)

Pull Request - State: closed - Opened by niklasf 8 months ago

#66 - Use constant-time base64 implementation

Pull Request - State: closed - Opened by niklasf 8 months ago

#65 - Work around symbol conflict between BoringSSL and OpenSSL

Pull Request - State: closed - Opened by niklasf 8 months ago - 1 comment

#64 - fix: check the server response size, should not be over 512kB

Pull Request - State: closed - Opened by pimeys 8 months ago - 4 comments

#63 - provide more detailed error info and align messages stylistically

Pull Request - State: closed - Opened by niklasf 8 months ago - 2 comments

#62 - Dependency `instant` is unmaintained

Issue - State: open - Opened by akatsukilevi 8 months ago - 1 comment

#61 - Bump deps

Pull Request - State: closed - Opened by Pi-Cla 9 months ago - 2 comments

#60 - Update documentation and example (close #59)

Pull Request - State: closed - Opened by naskya about 1 year ago - 1 comment

#59 - Documentation/Example improvements

Issue - State: closed - Opened by naskya about 1 year ago - 1 comment

#58 - Carve out a new release

Issue - State: closed - Opened by andyblarblar about 1 year ago - 4 comments

#57 - Add ability to create a new WebPushClient from a custom Isahc/hyper client (#56)

Pull Request - State: closed - Opened by naskya over 1 year ago - 4 comments

#56 - feature request: add ability to use proxy

Issue - State: closed - Opened by naskya over 1 year ago - 2 comments

#55 - Had to do this to get it to work

Pull Request - State: closed - Opened by phocks over 1 year ago - 1 comment

#54 - Show HTTP 400 body also if not structured like ErrorInfo

Pull Request - State: closed - Opened by niklasf over 1 year ago - 1 comment

#53 - Upgrade hyper client to stablised hyper 1.0 version/API

Issue - State: open - Opened by liamwh over 1 year ago - 1 comment

#52 - Add support for `Topic` header

Pull Request - State: closed - Opened by depressed-pho over 1 year ago - 3 comments

#51 - Web-push not working with chrome FCM

Issue - State: closed - Opened by summonmayank almost 2 years ago - 2 comments

#50 - Custom 'aud' claim is formatted incorrectly when added to JWT.

Issue - State: closed - Opened by summonmayank about 2 years ago
Labels: bug

#49 - Is it possible to use this library without OpenSSL?

Issue - State: closed - Opened by Hugo-Persson about 2 years ago - 1 comment

#48 - web-push fails if notification is to be sent to Firefox

Issue - State: closed - Opened by hamza1311 about 2 years ago - 2 comments

#47 - WebPushMessageBuilder::new needlessly returns result

Issue - State: closed - Opened by hamza1311 about 2 years ago - 1 comment

#46 - Add support to create a VapidSignatureBuilder from contents of a PEM file

Issue - State: closed - Opened by hamza1311 about 2 years ago - 4 comments

#45 - Also derive Copy for Urgency

Pull Request - State: closed - Opened by niklasf over 2 years ago - 1 comment

#44 - Add aesgcm support back, and fix some firefox bugs

Pull Request - State: closed - Opened by andyblarblar over 2 years ago

#43 - How to use this create.

Issue - State: closed - Opened by Dygear over 2 years ago - 7 comments

#42 - Determine which Push implimentations need aesgcm vs aes128gcm

Issue - State: closed - Opened by andyblarblar over 2 years ago - 5 comments
Labels: enhancement

#41 - Add support for `Topics` header

Issue - State: closed - Opened by andyblarblar over 2 years ago
Labels: enhancement

#40 - Test on Apple IOS devices

Issue - State: closed - Opened by andyblarblar over 2 years ago - 6 comments

#39 - Allow specifying the `Urgency` of each push message

Pull Request - State: closed - Opened by hpeebles over 2 years ago - 7 comments

#38 - The request is having invalid cryptographic keys

Issue - State: closed - Opened by Oreganon over 2 years ago - 2 comments

#37 - Allow to use web_push with neither the hyper nor the isahc client

Pull Request - State: closed - Opened by oliverbestmann over 2 years ago - 3 comments

#36 - v0.9.3

Pull Request - State: closed - Opened by andyblarblar over 2 years ago

#35 - How to supply private and public in Vapid key format?

Issue - State: closed - Opened by Hugo-Persson over 2 years ago - 9 comments

#34 - Make `WebPushClient` derive `Clone`

Issue - State: closed - Opened by wtho over 3 years ago - 2 comments

#32 - Add standard traits to public structs

Pull Request - State: closed - Opened by andyblarblar almost 4 years ago

#31 - Delegate jwt signing and remove many dependencies

Pull Request - State: closed - Opened by andyblarblar almost 4 years ago - 6 comments

#29 - Push v0.7.3 to crates.io

Issue - State: closed - Opened by andyblarblar about 4 years ago - 5 comments

#28 - Run tests on windows

Pull Request - State: closed - Opened by pimeys over 4 years ago

#27 - Replace CI with GitHub actions

Pull Request - State: closed - Opened by pimeys over 4 years ago

#26 - Put the client and firebase behind feature flags

Pull Request - State: closed - Opened by platy over 4 years ago - 6 comments

#25 - Make the crate work either with Tokio or async-std

Pull Request - State: closed - Opened by pimeys over 4 years ago - 8 comments

#24 - Fixes "unknown error encrypting the message"

Pull Request - State: closed - Opened by ChristophHess over 4 years ago - 2 comments

#23 - Adding Aes128Gcm support via `rust-ece` crate delegation

Pull Request - State: closed - Opened by tiesselune over 4 years ago - 17 comments

#22 - Dependency updates

Pull Request - State: closed - Opened by ChristophHess over 4 years ago - 2 comments

#21 - Doing some updating / maybe a fork

Issue - State: closed - Opened by platy over 4 years ago - 12 comments

#20 - Update simple_send.rs

Pull Request - State: closed - Opened by cheolgyu almost 5 years ago - 1 comment

#19 - Debugging help

Pull Request - State: closed - Opened by mohe2015 over 5 years ago - 1 comment

#18 - Can't get it to work with Firefox on Android

Issue - State: closed - Opened by mohe2015 over 5 years ago - 5 comments

#17 - Fixing null characters from end of the payload

Pull Request - State: closed - Opened by pimeys over 5 years ago - 3 comments

#16 - Message payload always ends with 16 NULL characters

Issue - State: closed - Opened by githubaccount624 over 5 years ago - 5 comments

#15 - No longer using tokio time feature

Pull Request - State: closed - Opened by niklasf over 5 years ago - 2 comments

#14 - Update to Ring 0.16

Pull Request - State: closed - Opened by pimeys over 5 years ago - 12 comments

#13 - Update ring dependency?

Issue - State: closed - Opened by githubaccount624 over 5 years ago - 3 comments

#12 - Add to web-push-libs organization

Issue - State: open - Opened by cubetastic33 over 5 years ago - 5 comments

#11 - Remove unused rust-crypto dependency (closes #10)

Pull Request - State: closed - Opened by niklasf almost 6 years ago - 1 comment

#10 - Replace rust-crypto dependency

Issue - State: closed - Opened by pythoneer almost 6 years ago - 2 comments

#9 - Async/await

Pull Request - State: closed - Opened by pimeys almost 6 years ago

#8 - web push without pem file.

Issue - State: closed - Opened by Jarves42 about 6 years ago - 2 comments

#7 - Update ring to 0.14

Pull Request - State: closed - Opened by thjread about 6 years ago - 2 comments

#6 - Fixed issue with implicit ttl being not valid

Pull Request - State: closed - Opened by JCapucho over 6 years ago - 7 comments

#5 - Change syntax to 2018 edition

Pull Request - State: closed - Opened by pimeys over 6 years ago

#4 - VAPID signing for aesgcm

Pull Request - State: closed - Opened by pimeys over 7 years ago - 2 comments

#3 - AES128GCM Support

Issue - State: closed - Opened by pimeys over 7 years ago - 2 comments

#2 - VAPID support

Issue - State: closed - Opened by pimeys over 7 years ago - 29 comments

#1 - Proper error handling for certain firebase responses

Pull Request - State: closed - Opened by pimeys almost 8 years ago