Fix CORS headers and wrangler.toml configuration

- Fixed wrangler.toml routes configuration for custom domains
- Enhanced CORS headers to match nginx configuration
- Added current branch to deploy.yaml for staging deployment
- Removed Access-Control-Allow-Credentials to fix security issue with wildcard origin

Author: sshrihar

.github/workflows/deploy.yaml

@@ -5,6 +5,7 @@ on:
     branches:
       - master
       - dev
+      - fix-cloudflare-deployment-scripts-update
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
@@ -22,7 +23,7 @@ jobs:
             export ENV=production
           fi
 
-          if [ "${{ github.ref_name }}" == "dev" ]; then
+          if [ "${{ github.ref_name }}" == "dev" ] || [ "${{ github.ref_name }}" == "fix-cloudflare-deployment-scripts-update" ]; then
             export ENV=staging
           fi
 

src/generateWorker.js

@@ -41,8 +41,7 @@ const corsHeaders = {
     "Access-Control-Allow-Origin": "*",
     "Access-Control-Allow-Methods": "GET, HEAD, POST, OPTIONS",
     "Access-Control-Allow-Headers": "Authorization,Accept,Origin,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range",
-    "Access-Control-Allow-Credentials": "true",
-    "Access-Control-Max-Age": "1728000",
+    "Access-Control-Max-Age": "86400", // 24 hours
 };
 
 // Auto-generated file mapping based on build directory contents