Hi,
On Windows I'm getting an error returned when attempting to upload a file to an Amazon AWS S3 bucket, using either the WinSCP app or just using the S3 upload interface via browser, pointing to my squid proxy.
I can download just fine, but not upload. ECAP is enabled for both the request and the response.
Here is the error:
A header you provided implies functionality that is not implemented
Extra Details: Header: Transfer-Encoding, RequestId: 3ED7C576056435A0, HostId: SU/9a+qN5rL79STErKgziygc2A34jLhWJ110qbUB1fele67wIZ5thMmgtNnKczBFVxuOy810HB4=
If I instead only specify to pass the response to my adapter via ECAP then the issue goes away.
So I captured the HTTP header for the success case and the failure case and narrowed it down the the failure case not specifying the length and specifying ",chunking" at the end. I assume if the request is passed to the adapter then the header has to be constructed at a time when the length of the file contents is not known? Hence has to use chunking.
I've indeed read a few forum links about just this issue, but confused as to whether chunking is supposed to finally work for 3.5.28 that I have or not. I compared to 4.x source and it looked basically the same.
I'll be needing to upload large files, too large to fit in memory, hence pretty sure chunking will be a requirement.
Is this is known issue? Any thoughts on solving it?
Thanks! I'm a Windows kernel filter driver developer so working open source is new to me. But with this forum's help I've had quite a lot of success. So thanks!
Russel McDonald
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
