HttpData source asset with method POST and proxyMethod set and HttpProxy destination on transfer uses the wrong method (GET instead of POST)

[lucian-torje-siemens]

Hello,
I'm working on proxying notifications through EDC scenario:

1. create an asset on provider side with data address similar to
   "dataAddress": { "properties": { "type": "HttpData", "baseUrl": "https://receiver.notifications.server.com/notifications", "method": "POST", "proxyMethod": true, "name": "", "contentType": "application/octet-stream" } }
2. create policy, contract for the above asset
3. negotiate contract on consumer side
4. note: consumer has the proxy endpoint set which will call the dataplane using the endpointdatareference data using POST with some extra payload (e.g. "{\"mynotificationdata\":\"data\"}") similar to https://github.com/florianrusch-zf/edc-notification-demo/blob/e020697da290a1e374ca67900ecd0eac622b1cbf/publisher-bds/src/main/java/net/catenax/edc/notification/connector/sdk/service/HttpProxyService.java#L42
5. start transfer using:
   "dataDestination": { "properties": { "type": "HttpProxy" } },
6. the proxy callback gets called, it calls the dataplane on the other side and the transfer starts
7. but instead doing POST https://receiver.notifications.server.com/notifications it calls GET https://receiver.notifications.server.com/notifications

My expectation is that there is a POST https://receiver.notifications.server.com/notifications made with the extra data added in the dataplane call payload - what am I doing wrong?

Related code:

EDC used https://github.com/eclipse-edc/Connector/tree/740c100ac162bc41b1968c232ad81f7d739aefa9

[lucian-torje-siemens]

Found it - By default a Jetty ContextHandler with a context of "/public" (like the dataplane) will actually redirect any request for "/public" to "/public/" if setAllowNullPathInfo is not set - see.