CAP Fiori Application filter query length exceeds the default HTTP GET request length limit

[MKM]

Hello Experts

We are developing a CAP Fiori application that displays a read-only report. The application retrieves data via an OData V4 service exposed from an ABAP backend.
 
The issue arises when user applies filters in the report. Since the backend metadata contains around 50 columns, the resulting query sometimes exceeds the default HTTP GET request length limit. As a result, the request automatically changes from GET to POST.
 
Although we include the CSRF token in the headers, the backend OData service responds with a "403 CSRF token missing" error when it receives the POST request. It seems the backend expects a CSRF token due to the method change but doesn"t recognize the token being sent.
 
Could you please advise on how to handle this situation or configure the system to avoid such errors?

Many Thanks,

Manoj