|
|
|
|
79
|
RNFB_ANDROID_PERMISSIONS=true react-native link
|
79
|
RNFB_ANDROID_PERMISSIONS=true react-native link
|
80
|
```
|
80
|
```
|
81
|
|
81
|
|
82
|
-pre 0.29 projects
|
|
|
|
|
82
|
+pre 0.29 projects
|
83
|
|
83
|
|
84
|
```sh
|
84
|
```sh
|
85
|
RNFB_ANDROID_PERMISSIONS=true rnpm link
|
85
|
RNFB_ANDROID_PERMISSIONS=true rnpm link
|
86
|
```
|
86
|
```
|
87
|
|
87
|
|
88
|
-The link script might not take effect if you have non-default project structure, please visit [the wiki](https://github.com/wkh237/react-native-fetch-blob/wiki/Manually-Link-Package/_edit) to manually link the pacakge.
|
|
|
|
|
88
|
+The link script might not take effect if you have non-default project structure, please visit [the wiki](https://github.com/wkh237/react-native-fetch-blob/wiki/Manually-Link-Package) to manually link the pacakge.
|
89
|
|
89
|
|
90
|
**Grant Permission to External storage for Android 5.0 or lower**
|
90
|
**Grant Permission to External storage for Android 5.0 or lower**
|
91
|
|
91
|
|
|
|
|
|
154
|
- To send a form data, the `Content-Type` header does not matters. When the body is an `Array` we will set proper content type for you.
|
154
|
- To send a form data, the `Content-Type` header does not matters. When the body is an `Array` we will set proper content type for you.
|
155
|
- To send binary data, you have two choices, use BASE64 encoded string or path points to a file contains the body.
|
155
|
- To send binary data, you have two choices, use BASE64 encoded string or path points to a file contains the body.
|
156
|
- If the `Content-Type` containing substring`;BASE64` or `application/octet` the given body will be considered as a BASE64 encoded data which will be decoded to binary data as the request body.
|
156
|
- If the `Content-Type` containing substring`;BASE64` or `application/octet` the given body will be considered as a BASE64 encoded data which will be decoded to binary data as the request body.
|
157
|
- - Otherwise, if a string starts with `RNFetchBlob-file://` (which can simply done by `RNFetchBlob.wrap(PATH_TO_THE_FILE)`), it will try to find the data from the URI string after `RNFetchBlob-file://` and use it as request body.
|
|
|
|
|
157
|
+ - Otherwise, if a string starts with `RNFetchBlob-file://` (which can simply done by `RNFetchBlob.wrap(PATH_TO_THE_FILE)`), it will try to find the data from the URI string after `RNFetchBlob-file://` and use it as request body.
|
158
|
- To send the body as-is, simply use a `Content-Type` header not containing `;BASE64` or `application/octet`.
|
158
|
- To send the body as-is, simply use a `Content-Type` header not containing `;BASE64` or `application/octet`.
|
159
|
|
159
|
|
160
|
-> It is Worth to mentioning that the HTTP request uses cache by default, if you're going to disable it simply add a Cache Control header `'Cache-Control' : 'no-store'`
|
|
|
|
|
160
|
+> It is Worth to mentioning that the HTTP request uses cache by default, if you're going to disable it simply add a Cache Control header `'Cache-Control' : 'no-store'`
|
161
|
|
161
|
|
162
|
> After 0.9.4, we disabled `Chunked` transfer encoding by default, if you're going to use it, you should explicitly set header `Transfer-Encoding` to `Chunked`.
|
162
|
> After 0.9.4, we disabled `Chunked` transfer encoding by default, if you're going to use it, you should explicitly set header `Transfer-Encoding` to `Chunked`.
|
163
|
|
163
|
|
|
|
|
|
380
|
|
380
|
|
381
|
### Upload/Download progress
|
381
|
### Upload/Download progress
|
382
|
|
382
|
|
383
|
-In `version >= 0.4.2` it is possible to know the upload/download progress. After `0.7.0` IOS and Android upload progress are also supported.
|
|
|
|
|
383
|
+In `version >= 0.4.2` it is possible to know the upload/download progress. After `0.7.0` IOS and Android upload progress are also supported.
|
384
|
|
384
|
|
385
|
```js
|
385
|
```js
|
386
|
RNFetchBlob.fetch('POST', 'http://www.example.com/upload', {
|
386
|
RNFetchBlob.fetch('POST', 'http://www.example.com/upload', {
|
|
|
|
|
737
|
|
737
|
|
738
|
**Read Stream Event Overhead**
|
738
|
**Read Stream Event Overhead**
|
739
|
|
739
|
|
740
|
-When reading data via `fs.readStream` the process seems blocking JS thread when file is large, it's because the default buffer size is quite small (4kb) which result in large amount of events triggered in JS thread, try to increase the buffer size (for example 100kb = 102400) and set a larger interval (which is introduced in 0.9.4 default value is 10ms) to limit the frequency.
|
|
|
|
|
740
|
+When reading data via `fs.readStream` the process seems blocking JS thread when file is large, it's because the default buffer size is quite small (4kb) which result in large amount of events triggered in JS thread, try to increase the buffer size (for example 100kb = 102400) and set a larger interval (which is introduced in 0.9.4 default value is 10ms) to limit the frequency.
|
741
|
|
741
|
|
742
|
**Reduce RCT Bridge and BASE64 Overhead**
|
742
|
**Reduce RCT Bridge and BASE64 Overhead**
|
743
|
|
743
|
|