HTTP Proxy implementation

[lgblaumeiser]

WHAT

The current HTTP proxy implementation upstream has some shortcomings. Major issue is, that depending on the situation, masking a 4xx error coming from the backend by translating it into a 500 status code can be the right thing to do as it indicates a configuration error on the provider side, or wrong, as the status code was motivated by a user error. Currently, in the proxy masks all 4xx status codes to 500.

Based on a request to upstream, a discussion arose which will lead to a decision of the upstream committer group soon. Based on this decision, downstream activities will be needed to keep the functionality of a HTTP proxy with improved status code handling.

WHY

To keep the HTTP proxy functionality stable although upstream changes will occur.

HOW

The downstream implementation should be based on the upstream code base.

[arnoweiss]

Can you link the upstream discussion?

[lgblaumeiser]

@ndr-brt , is there any documentation of the upstream discussion/decision?

[ndr-brt]

@arnoweiss Discussion happened during the committer group meeting, this is the Decision Record:
eclipse-edc/Connector#4805

[arnoweiss]

Oh wow, that goes quite a bit further than this ticket. Thanks for the link.