com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
com\citrix\sharefile\api\https\SFUploadRunnable.java:  "ChunkUri": "https://storage-ec2-34.sharefile.com/upload-streaming-2.aspx?batchid=723ffb79-d720-4de8-b95d-087be1e6462a&overwrite=true&uploadid=rsu-9c48c04a5fb84f9d8fc93875231b01ca&raw=1&encparams=phT2SuROQY1XrVtmjxwO2yRkHK2uBy1BtAjWhNYAu-lvRQr3eTm-Xh6zYbz3Lc9FfRoDvzBCdI7SyPDVrxL0bR9-cb7IsTFbIcnPRRJ8xLn0nJ0yxIeKXV-m-gb0HWzHGdHOnKTBEEgwD969n-8rbXu6jvkZ3UhEwY6I79GfdTogsf1vi7lFrfPrTe8TV5isPOPSpSINN3qxBI_qWJoy8D_AUnK009vuFHJP4t9yzPi6rDqmfU-7ZhmhncG4rsBfTdEWL3wQiOdU5kNnFl5WkSzjO8dg1vmjSidVSreUN_YJeQw95i8w5XaVA7BGuWDDNXjE8rV53cyQ9p2blo6Xovj4fxQi6wSf0J6CqLKZnFgbHTd7IVvexhdXhTMYAWce01eMBr7iWD9Kd2J3O_nLX3oEWKMDgqCg6SCSd8baO9_EBiQ8QnDwfh8tWeOQq60_gXeX-wBn_TAPNUPTmV1RyD5nt9sn5Q77Rd6YtiOiSjNI98z2mCTSiLp3TYMm4gB38CawObllVnJuWIERHKGbyEwJhE5PNxdMQC4PeM4$",
com\citrix\sharefile\api\https\SFUploadRunnable.java:			final String finalURL = mUploadSpecification.getChunkUri() + append;
com\citrix\sharefile\api\https\SFUploadRunnable.java:			Logger.d(TAG, "POST " + mUploadSpecification.getChunkUri());
com\citrix\sharefile\api\models\SFUploadSpecification.java:	@SerializedName("ChunkUri")
com\citrix\sharefile\api\models\SFUploadSpecification.java:	private URI ChunkUri;
com\citrix\sharefile\api\models\SFUploadSpecification.java:	public URI getChunkUri() {
com\citrix\sharefile\api\models\SFUploadSpecification.java:		return this.ChunkUri;
com\citrix\sharefile\api\models\SFUploadSpecification.java:	public void setChunkUri(URI chunkuri) {
com\citrix\sharefile\api\models\SFUploadSpecification.java:		this.ChunkUri = chunkuri;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* must append the parameters index, byteOffset and hash to the ChunkUri address. Index is a
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* If using the Threaded Uploader, the client can add the parameter fmt=json to the ChunkUri
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* calls to the ChunkUri starting from the position represented by the values of ResumeIndex and
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* append the parameters index, offset and hash to the end of the ChunkUri address. Index
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the end of ChunkUri, as explained in Streamed. After all chunks were sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* ensure the file has not been modified; and continue issuing ChunkUri calls from the ResumeIndex
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:  "ChunkUri": "https://storage-ec2-34.sharefile.com/upload-streaming-2.aspx?batchid=723ffb79-d720-4de8-b95d-087be1e6462a&overwrite=true&uploadid=rsu-9c48c04a5fb84f9d8fc93875231b01ca&raw=1&encparams=phT2SuROQY1XrVtmjxwO2yRkHK2uBy1BtAjWhNYAu-lvRQr3eTm-Xh6zYbz3Lc9FfRoDvzBCdI7SyPDVrxL0bR9-cb7IsTFbIcnPRRJ8xLn0nJ0yxIeKXV-m-gb0HWzHGdHOnKTBEEgwD969n-8rbXu6jvkZ3UhEwY6I79GfdTogsf1vi7lFrfPrTe8TV5isPOPSpSINN3qxBI_qWJoy8D_AUnK009vuFHJP4t9yzPi6rDqmfU-7ZhmhncG4rsBfTdEWL3wQiOdU5kNnFl5WkSzjO8dg1vmjSidVSreUN_YJeQw95i8w5XaVA7BGuWDDNXjE8rV53cyQ9p2blo6Xovj4fxQi6wSf0J6CqLKZnFgbHTd7IVvexhdXhTMYAWce01eMBr7iWD9Kd2J3O_nLX3oEWKMDgqCg6SCSd8baO9_EBiQ8QnDwfh8tWeOQq60_gXeX-wBn_TAPNUPTmV1RyD5nt9sn5Q77Rd6YtiOiSjNI98z2mCTSiLp3TYMm4gB38CawObllVnJuWIERHKGbyEwJhE5PNxdMQC4PeM4$",
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:			final String finalURL = mUploadSpecification.getChunkUri() + append;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:			Logger.d(TAG, "POST " + mUploadSpecification.getChunkUri());
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:	@SerializedName("ChunkUri")
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:	private URI ChunkUri;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:	public URI getChunkUri() {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		return this.ChunkUri;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:	public void setChunkUri(URI chunkuri) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		this.ChunkUri = chunkuri;
ShareFileV3SampleSE.java:			JsonElement element = uploadConfig.get("ChunkUri");
