[PR #1312] [MERGED] Consider aes128gcm content encoding as an indicator for UnifiedPush #1562

New issue

Closed

opened 2026-05-07 01:02:41 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:02:41 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/binwiederhier/ntfy/pull/1312
Author: @vkrause
Created: 4/7/2025
Status: ✅ Merged
Merged: 5/21/2025
Merged by: @binwiederhier

Base: main ← Head: work/vkrause/detect-encrypted-messages-as-unified-push

📝 Commits (1)

bd08a12 Consider aes128gcm content encoding as an indicator for UnifiedPush

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 server/server.go (+2 -1)

📄 Description

Without this a UnifiedPush/Web Push message with encryption would be turned into an attachment. That in itself isn't pretty but can still work, but it requires attachments to be enabled in the first place.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/binwiederhier/ntfy/pull/1312 **Author:** [@vkrause](https://github.com/vkrause) **Created:** 4/7/2025 **Status:** ✅ Merged **Merged:** 5/21/2025 **Merged by:** [@binwiederhier](https://github.com/binwiederhier) **Base:** `main` ← **Head:** `work/vkrause/detect-encrypted-messages-as-unified-push` --- ### 📝 Commits (1) - [`bd08a12`](https://github.com/binwiederhier/ntfy/commit/bd08a120cda0949769225f197fbd947245703018) Consider aes128gcm content encoding as an indicator for UnifiedPush ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `server/server.go` (+2 -1) </details> ### 📄 Description Without this a UnifiedPush/Web Push message with encryption would be turned into an attachment. That in itself isn't pretty but can still work, but it requires attachments to be enabled in the first place. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>