Github user cozzbie commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
Issue seems to be mostly an android problem because same code works fine on
iOS. Using @cooperjbrandon advice and adding `options.chunkedMode = false;` to
just the android code
Github user cooperjbrandon commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
@daserge 1.6.2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user daserge commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
@cooperjbrandon what is your plugin version?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user cooperjbrandon commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
I have this same exact issue trying to upload to s3. I also got the error
message :
```
You must provide the Content-Length HTTP header.
```
TLDR:
Github user craig-at-rsg commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
@raykin Haven't found a workaround - reverted to the older version of this
plugin.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user vukdavid commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
Facing same HTTP 411 issue: "A request with the POST method requires a
valid Content-Length header."
Using android with latest plugin versions:
Github user raykin commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
same here.
```shell
E/FileTransfer(22411):
Github user craig-at-rsg commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
This fix is creates a problem for WSGI applications - before this fix, they
would happily accept chunked transfers, but after they return status 411 and
complain about a
Github user royipr commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
cool Ill check that later today!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user daserge commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
Oh, I think it might switch to `chunkedMode=true` because of HTTPS:
Github user royipr commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
I have tested that on 6.0.1, Sounds weird what you saying...
I thought it might be related to AWS but if version 1.5.1 worked, there
must be something broken with 1.6. If you
Github user daserge commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
I've tested the file-transfer tests via logging out the headers from
whatheaders.com (in filetransfer.spec.27) and from local server headers echo
endpoint (in `chunkedMode
Github user royipr commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
@daserge Acourding to the response it does attach Transfer-Encoding header.
Is there a way to print the headers? I didn't saw them on `adb logcat`.
Maybe the problem
Github user daserge commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
@royipr - does it attach `Transfer-Encoding` for `chunkedMode: false`?
It should do the opposite according to [the
Github user royipr commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/141
Hi.
I think I found a bug regarding the issue..
When trying to upload a file with `chuckedMode: false` it seems to attach a
`Transfer-Encoding` header by default.
15 matches
Mail list logo
