Skip to content

chore: Set AES128GCM as default encoding#222

Merged
martijndwars merged 1 commit intoweb-push-libs:masterfrom
swiftsjh02:chore
Jul 6, 2025
Merged

chore: Set AES128GCM as default encoding#222
martijndwars merged 1 commit intoweb-push-libs:masterfrom
swiftsjh02:chore

Conversation

@swiftsjh02
Copy link
Contributor

@swiftsjh02 swiftsjh02 commented Jul 4, 2025

Summary

This PR changes the default encryption encoding used in the PushService class from AESGCM to AES128GCM.

Rationale

While AESGCM is a newer encoding method, some modern browsers (e.g., Chrome, Edge) currently do not properly trigger service workers when receiving push notifications encoded with aesgcm.

By contrast, aes128gcm is widely supported and works reliably across all major browsers. This change ensures more consistent and reliable push notification delivery.

Changes

  • Updated the send(Notification) method in PushService to use Encoding.AES128GCM by default.

Reference

##Notes

  • This is My First Contribution , Give any Opinion And Advice Freely.

@martijndwars
Copy link
Member

Thanks!

@martijndwars martijndwars merged commit d44851e into web-push-libs:master Jul 6, 2025
@danielerneBIT
Copy link

@martijndwars Could you push 5.2.0 to maven repository as well?

@martijndwars
Copy link
Member

Maven Central changed their integration and we need to update some plugins -- hope to get to it later this week!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants