docs: new features documented

Author: AidasK

README.md

@@ -83,7 +83,8 @@ For every request, you can confirm reception in HTTP status codes (can be change
 Enabling the `testChunks` option will allow uploads to be resumed after browser restarts and even across browsers (in theory you could even run the same file upload across multiple tabs or different browsers).  The `POST` data requests listed are required to use Flow.js to receive data, but you can extend support by implementing a corresponding `GET` request with the same parameters:
 
 * If this request returns a `200` HTTP code, the chunks is assumed to have been completed.
-* If the request returns anything else, the chunk will be uploaded in the standard fashion.
+* If request returns a permanent error status, upload is stopped.
+* If request returns anything else, the chunk will be uploaded in the standard fashion.
 
 After this is done and `testChunks` enabled, an upload can quickly catch up even after a browser restart by simply verifying already uploaded chunks that do not need to be uploaded again.
 
@@ -113,6 +114,8 @@ function, it will be passed a FlowFile, a FlowChunk and isTest boolean (Default:
  include cookies as part of the request, you need to set the `withCredentials` property to true.
 (Default: `false`)
 * `method` Method to use when POSTing chunks to the server (`multipart` or `octet`) (Default: `multipart`)
+* `testMethod` HTTP method to use when chunks are being tested. If set to a function, it will be passed a FlowFile and a FlowChunk arguments. (Default: `GET`)
+* `uploadMethod` HTTP method to use when chunks are being uploaded. If set to a function, it will be passed a FlowFile and a FlowChunk arguments. (Default: `GET`)
 * `prioritizeFirstAndLastChunk` Prioritize first and last chunks of all files. This can be handy if you can determine if a file is valid for your service from only the first or last chunk. For example, photo or video meta data is usually located in the first part of a file, making it easy to test support from only the first chunk. (Default: `false`)
 * `testChunks` Make a GET request to the server for each chunks to see if it already exists. If implemented on the server-side, this will allow for upload resumes even after a browser crash or even a computer restart. (Default: `true`)
 * `preprocess` Optional function to process each chunk before testing & sending. Function is passed the chunk as parameter, and should call the `preprocessFinished` method on the chunk when finished. (Default: `null`)
@@ -125,6 +128,9 @@ to 0 to handle each progress callback. (Default: `500`)
 and average upload speed wil be equal to current upload speed. For longer file uploads it is
 better set this number to 0.02, because time remaining estimation will be more accurate. This
 parameter must be adjusted together with `progressCallbacksInterval` parameter. (Default 0.1)
+* `successStatuses` Response is success if response status is in this list (Default: `[200,201,
+202]`)
+* `permanentErrors` Response fails if response status is in this list (Default: `[404, 415, 500, 501]`)
 
 
 #### Properties
@@ -166,21 +172,24 @@ parameter must be adjusted together with `progressCallbacksInterval` parameter.
 
 #### Events
 
-* `.fileSuccess(file, message)` A specific file was completed. First argument `file` is instance of `FlowFile`, second argument `message` contains server response. Response is always a string.
-* `.fileProgress(file)` Uploading progressed for a specific file.
+* `.fileSuccess(file, message, chunk)` A specific file was completed. First argument `file` is instance of `FlowFile`, second argument `message` contains server response. Response is always a string. 
+Third argument `chunk` is instance of `FlowChunk`. You can get response status by accessing xhr 
+object `chunk.xhr.status`.
+* `.fileProgress(file, chunk)` Uploading progressed for a specific file.
 * `.fileAdded(file, event)` This event is used for file validation. To reject this file return false.
 This event is also called before file is added to upload queue,
 this means that calling `flow.upload()` function will not start current file upload.
 Optionally, you can use the browser `event` object from when the file was
 added.
 * `.filesAdded(array, event)` Same as fileAdded, but used for multiple file validation.
 * `.filesSubmitted(array, event)` Can be used to start upload of currently added files.
-* `.fileRetry(file)` Something went wrong during upload of a specific file, uploading is being retried.
-* `.fileError(file, message)` An error occurred during upload of a specific file.
+* `.fileRetry(file, chunk)` Something went wrong during upload of a specific file, uploading is being 
+retried.
+* `.fileError(file, message, chunk)` An error occurred during upload of a specific file.
 * `.uploadStart()` Upload has been started on the Flow object.
 * `.complete()` Uploading completed.
 * `.progress()` Uploading progress.
-* `.error(message, file)` An error, including fileError, occurred.
+* `.error(message, file, chunk)` An error, including fileError, occurred.
 * `.catchAll(event, ...)` Listen to all the events listed above with the same callback function.
 
 ### FlowFile