From 742c3d3959e163c08f8263cfed26ed0e7706784a Mon Sep 17 00:00:00 2001
From: Eric <eric@digitribe.fr>
Date: Mon, 11 May 2026 11:18:48 -0400
Subject: [PATCH] =?UTF-8?q?fix:=20Suppression=20header=20Origin=20forc?=
 =?UTF-8?q?=C3=A9=20pour=20GeoServer?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le header Origin forcé dans le middleware Traefik causait un 400
'Origin does not correspond to request' de Tomcat/GeoServer.
Solution: laisser le navigateur envoyer son Origin naturellement
+ activation du filtre CORS Tomcat dans web.xml de GeoServer
---
 dynamic/routes.yml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/dynamic/routes.yml b/dynamic/routes.yml
index 4e08bd3..a625cbd 100644
--- a/dynamic/routes.yml
+++ b/dynamic/routes.yml
@@ -5,7 +5,6 @@ http:
         customRequestHeaders:
           X-Forwarded-Host: "geoserver.digitribe.fr"
           X-Forwarded-Proto: "https"
-          Origin: "https://geoserver.digitribe.fr"
     geoserver-redirect:
       replacePath:
         path: "/geoserver/"