fix: sentry cors tunnel

SocialGouv · Jan 28, 2025 · d6fe9a5 · d6fe9a5
1 parent 8a6556a
commit d6fe9a5
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 8 deletions.
diff --git a/.kontinuous/values.yaml b/.kontinuous/values.yaml
@@ -22,12 +22,6 @@ x-secure-headers: &headers >-
 
   more_set_headers "Cross-Origin-Opener-Policy: same-origin";
 
-  location /api/monitoring {
-    more_set_headers "Access-Control-Allow-Origin: *";
-    more_set_headers "Access-Control-Allow-Methods: POST, OPTIONS";
-    more_set_headers "Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, sentry-trace";
-  }
-
 global:
   pgSecretName: pg-app
 

diff --git a/packages/app/next.config.js b/packages/app/next.config.js
@@ -118,7 +118,7 @@ module.exports = withSentryConfig(
     transpileClientSDK: true,
 
     // Routes browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers and CORS issues
-    tunnelRoute: "/api/monitoring",
+    tunnelRoute: "/monitoring",
 
     // Don't hide source maps from generated client bundles
     hideSourceMaps: false,

diff --git a/packages/app/sentry.client.config.ts b/packages/app/sentry.client.config.ts
@@ -11,7 +11,7 @@ const IS_PRODUCTION = ENVIRONMENT === "production";
 Sentry.init({
   dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
   environment: ENVIRONMENT,
-  tunnel: "/api/monitoring",
+  tunnel: "/monitoring",
 
   // Optimal sample rates based on environment
   tracesSampleRate: IS_PRODUCTION ? 0.1 : 1.0,