You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS complains with 501 Not Implemented and response body like:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>NotImplemented</Code><Message>A header you provided implies functionality that is not implemented</Message><Header>Transfer-Encoding</Header><RequestId>qwerty</RequestId><HostId>qwerty</HostId></Error>
Expected Behavior
Response code 200 OK when using dataplane sink to push data to AWS S3
Observed Behavior
Failure to create the new file due to 501 http status
Steps to Reproduce
Steps to reproduce the behavior:
Create asset with data destination baseUrl as an AWS S3 presigned upload url
* bug: sending data to an AWS S3 presigned upload url does not work eclipse-edc#1643
* fix checkstyle
* bug: fix sample assets and add missing properties
* switch build env
* fix checkstyle
* documentation
* apply review from @jimmarino
* fix checkstyle
* fix test
* apply review - rename to transferInOneGo and reverse logic
* fix test
* use transfer in one go
* update postman
* adjust policy - add more tests
* fix checkstyle
* add logging (to be reverted)
* Revert "add logging (to be reverted)"
This reverts commit 870ecd0.
…url (#1645)
* bug: sending data to an AWS S3 presigned upload url does not work #1643
* fix checkstyle
* documentation
* apply review from @jimmarino
* fix checkstyle
* fix test
* apply review - rename to transferInOneGo and reverse logic
* fix test
* apply review from @jimmarino - rename to "transfer in one go" to "nonChunkedTransfer"
* apply review
* fix changelog for proper milestone
* fix NonChunkedTransferRequestBodyTest.java - use the new faker import
Co-authored-by: Andrei-Laurentiu Coman <andrei.coman@siemens.com>
Bug Report
Describe the Bug
AWS complains with 501 Not Implemented and response body like:
Expected Behavior
Response code 200 OK when using dataplane sink to push data to AWS S3
Observed Behavior
Failure to create the new file due to 501 http status
Steps to Reproduce
Steps to reproduce the behavior:
Context Information
Using the latest EDC code from branch main
Detailed Description
The problem is within OkHttp implementation
see OkHttp Transfer Encoding search
Possible Implementation
A new property called chunked: true/false that would allow sending the data as a all or as stream (in chunks)
The text was updated successfully, but these errors were encountered: