web-push-csharp
web-push-csharp copied to clipboard
Web Push library for C#
Me and my team have been trying to implement the web push notifications with our .NET 6 backend. When ran on localhost, everything works perfectly. Pushing and receiving a notification...
StatusCode: 406, ReasonPhrase: 'Not Acceptable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Retry-After: 900 X-WNS-NOTIFICATIONSTATUS: appthrottled X-WNS-STATUS: appthrottled X-WNS-MSG-ID: 331FA2FC1F350267 X-WNS-DEBUG-TRACE: SG2PEPF0005589B MS-CV: 7m+MIF/zukuEsvNq7wwnBA.0 Strict-Transport-Security: max-age=31536000; includeSubDomains Date: Tue, 19 Jul...
Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 10.0.3 to 13.0.1. Release notes Sourced from Newtonsoft.Json's releases. 13.0.1 New feature - Add JsonSelectSettings with configuration for a regex timeout Change - Remove portable assemblies from...
Currently, the project uses This version has a security alert https://github.com/bcgit/bc-csharp/wiki/CVE-2020-15522
It is impossible to use this library in strong named applications, because it does not have strong name. Also, there are no sense to use netcoreapp1.0;netcoreapp1.1;netcoreapp2.0 as target frameworks, this...
- Updated RichardSzalay.MockHttp to 6.0.0 (it's strong name signed) - Updated .Net 4.5 to .Net 4.5.2 (otherwise I can't compile with VS 2022) - Added .NET 6.0 To sign an...
After I delete Visual studio 2019, when the trial has been over, There is no option to download .NETstandard anymore from the network so the project can't be built anymore...
Remove BouncyCastle dependency to use System.Security.Cryptography. Add .net48 support Remove .netstandard1.1 et .netstandard2.0 don't support all crypto methods
You are only using json serialization in the JwsSigner.cs class. Why not get rid of the heavy dependency Newtonsoft.Json and use the standard fast and simple JsonSerializer ([Documentation](https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-how-to?pivots=dotnet-5-0#how-to-write-net-objects-as-json-serialize))
I tried the sample code for the edge endpoint (with the link https://sg2p.notify.windows.com/w/?token=...), but the error (Unexpected error) occurred. So, I add the below code, and it can be run...