SAP / SAP/cloud-sdk-java

Newly introduced `CsrfTokenInterceptor` is producing large amount of warning logs

Offen
#1,270 3 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@ricardosrib arbeitet bereits daran.

Seit 14.9.2026.

bug
Vorherrschende Sprache
Java
Sterne
41
Forks
33
Ø Merge
18 Std. 34 Min.
Gemergte PRs (30 T.)
19

Beschreibung

Describe the Bug

We are consuming the com.sap.cloud.sdk.sdk-bom dependency in our CAP Java microservices. We recently upgraded to version 5.34.0 (from 5.33.0) and started to observe a large amount of warning logs of type: “Target system did not respond with a x-csrf-token header. The subsequent request may fail if a CSRF token is required.” Those seem to originate from the newly introduced CsrfTokenInterceptor.

Unfortunately, we could not find any additional information regarding this change in the release notes or similar. Apart from this, we have some concerns that this results in a big number of requests that are now emitted from this class to the request source to obtain the csrf header.

Best regards,
Felix Starke

Steps to Reproduce

As we are working on an SAP internal project, kindly reach out for further information or discussions.

Expected Behavior

Can you please clarify the need of having this Interceptor and this being an actual warning log. Furthermore, kindly clarify that the amount of HEAD-requests triggered by this is necessary.

Screenshots

No response

Used Versions
  • Java and Maven version via mvn --version: ...
  • SAP Cloud SDK version: 5.34.0
  • Spring Boot or CAP version: Spring Boot 3.5.17 with CDS Services 4.9.4
Code Examples

No response

Stack Trace

No response

Log File

No response

Affected Development Phase

Production

Impact

Impaired

Timeline

No response

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.