refactor: delegate security to CloudFlare and clean up mailgun-webhook
Remove application-level CORS and IP whitelisting as security is now handled at CloudFlare edge. CORS is not applicable for backend webhook service, and IP whitelisting is more effectively managed at infrastructure layer. Also translate Dockerfile comments to English and add registry URL to build script. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -133,7 +133,7 @@ For **unsubscribed** events:
|
||||
### Future Enhancements
|
||||
For production deployment, consider:
|
||||
- **Signature Verification**: Verify webhook authenticity using `timestamp`, `token`, and `signature`
|
||||
- **IP Whitelisting**: Restrict to MailGun's IP ranges
|
||||
- **IP Whitelisting**: Restrict to MailGun's IP ranges (implemented via CloudFlare)
|
||||
- **Rate Limiting**: Prevent abuse
|
||||
|
||||
## Database Integration
|
||||
|
||||
Reference in New Issue
Block a user