|  | @@ -157,6 +157,8 @@ To sum up :
 | 
	
		
			
			| 157 | 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 | 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'` 
 | 
	
		
			
			|  | 161 | +
 | 
	
		
			
			| 160 | 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`.
 | 
	
		
			
			| 161 | 163 |  
 | 
	
		
			
			| 162 | 164 |  ### Download example : Fetch files that needs authorization token
 |