OpenBankingToolkit / openbanking-reference-implementation

ForgeRock OpenBanking Reference Implementation is an example of how you can bundle all the micro-services together to create an Open Banking eco-system
Apache License 2.0
7 stars 4 forks source link

Error max response HTTP Header Size on httpclient #369

Closed jsanhc closed 3 years ago

jsanhc commented 3 years ago

Describe the bug

}

- But running the functional tests some tests and such as example the test `PollAndAcknowledgeAggregatedPollingTest` it's raise the below error:
```json
{
  "timestamp": "2021-02-18T15:30:35.766+0000",
  "path": "/open-banking/v3.1.6/events",
  "status": 500,
  "error": "Internal Server Error",
  "message": "HTTP header is larger than 8192 bytes."
}

To Reproduce Steps to reproduce the behaviour:

  1. run the test PollAndAcknowledgeAggregatedPollingTest against master.
  2. See error

Expected behaviour No error.

Current behaviour Error.

Workaround

Code analysis

Release Notes

Affected App: Gateway app.

jsanhc commented 3 years ago

Implemented Solution

svankamamidi commented 2 years ago

Implemented Solution

  • Upgraded spring cloud version Greenwich.SR1 to Greenwich.SR6 in openbanking-parent this latest spring cloud version have the dependency version 2.1.5 of gateway-core with the fix to set the max header size as a httpClient property for responses.
  • Added max-header-size property in the application.yml file in reference-implementation/openbanking-config.
#Spring cloud config
spring:
  ...
  cloud:
    ...
      ...
    gateway:
      httpclient:
        max-header-size: 10000000 # The max response header size, Required for the large signed JWT headers

Check projects openbanking-parent pom integrity after upgrade spring-cloud framework to Greenwich.SR6 to fix max header size on the response (HttpClient)

this solution is not working for us. We are using Spring Boot 2.7.2