[PR #780] [MERGED] fix: exclude telegram routes from x-custom-auth check #757

New issue

Closed

opened 2026-02-26 21:32:50 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 21:32:50 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dreamhunter2333/cloudflare_temp_email/pull/780
Author: @dreamhunter2333
Created: 12/11/2025
Status: ✅ Merged
Merged: 12/11/2025
Merged by: @dreamhunter2333

Base: main ← Head: feature/email

📝 Commits (1)

b80c9a8 fix: exclude telegram routes from x-custom-auth check

📊 Changes

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

View changed files

📝 worker/src/worker.ts (+1 -1)

📄 Description

User description

Summary

Exclude /telegram/ routes from x-custom-auth header check
Telegram webhook and API calls can now function without custom auth password
Telegram API has its own authentication via bot tokens

Test plan

Verify telegram webhook still works when PASSWORDS is configured
Verify other routes still require x-custom-auth when enabled

🤖 Generated with Claude Code

PR Type

Bug fix

Description

Exclude /telegram/ routes from x-custom-auth header check.
Ensure Telegram API calls function without custom auth.
Maintain authentication for other routes with x-custom-auth.
Simplify integration for Telegram webhook and bot token authentication.

Changes walkthrough 📝

Relevant files

Bug fix

worker.ts

Exclude `/telegram/` routes from custom auth check

worker/src/worker.ts

Added condition to exclude /telegram/ routes from x-custom-auth check.

Ensured other routes still validate x-custom-auth when required.

+1/-1

Need help?
Type /help how to ... in the comments thread for any questions about PR-Agent usage.
Check out the documentation for more information.

_{🔄 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/dreamhunter2333/cloudflare_temp_email/pull/780 **Author:** [@dreamhunter2333](https://github.com/dreamhunter2333) **Created:** 12/11/2025 **Status:** ✅ Merged **Merged:** 12/11/2025 **Merged by:** [@dreamhunter2333](https://github.com/dreamhunter2333) **Base:** `main` ← **Head:** `feature/email` --- ### 📝 Commits (1) - [`b80c9a8`](https://github.com/dreamhunter2333/cloudflare_temp_email/commit/b80c9a8b97d53937e03c314cdda7598c59efc7d8) fix: exclude telegram routes from x-custom-auth check ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `worker/src/worker.ts` (+1 -1) </details> ### 📄 Description ### **User description** ## Summary - Exclude `/telegram/` routes from `x-custom-auth` header check - Telegram webhook and API calls can now function without custom auth password - Telegram API has its own authentication via bot tokens ## Test plan - [ ] Verify telegram webhook still works when `PASSWORDS` is configured - [ ] Verify other routes still require `x-custom-auth` when enabled 🤖 Generated with [Claude Code](https://claude.com/claude-code) ___ ### **PR Type** Bug fix ___ ### **Description** - Exclude `/telegram/` routes from `x-custom-auth` header check. - Ensure Telegram API calls function without custom auth. - Maintain authentication for other routes with `x-custom-auth`. - Simplify integration for Telegram webhook and bot token authentication. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Bug fix</strong></td><td><table> <tr> <td> <details> <summary><strong>worker.ts</strong><dd><code>Exclude `/telegram/` routes from custom auth check</code>              </dd></summary> <hr> worker/src/worker.ts <li>Added condition to exclude <code>/telegram/</code> routes from <code>x-custom-auth</code> check.<br> <li> Ensured other routes still validate <code>x-custom-auth</code> when required. </details> </td> <td><a href="https://github.com/dreamhunter2333/cloudflare_temp_email/pull/780/files#diff-c007030a206d7e4e2a4879ba673551e7633ad914b67cfac204096edced3f80a2">+1/-1</a>      </td> </tr> </table></td></tr></tr></tbody></table> ___ > <details> <summary> Need help?</summary><li>Type <code>/help how to ...</code> in the comments thread for any questions about PR-Agent usage.</li><li>Check out the <a href="https://qodo-merge-docs.qodo.ai/usage-guide/">documentation</a> for more information.</li></details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>