SAP / SAP/cloud-sdk-java

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

Abierto
#1,270 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@ricardosrib ya está trabajando en esto.

Desde el 14/9/2026.

bug
Lenguaje dominante
Java
Estrellas
41
Forks
33
Merge medio
18 h 34 min
PR fusionados (30 d)
19

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.