Many “Failed to parse Content-Range header…” messages

I’m looking at the activity log and see a lot of “failed to parse…” messages. Is this normal? How does one know that we can trust these restore points created by WP Time Capsule? Is there a way to test? Or can you make a demo video of what a restore procedure looks like? I’m ready to use this type of plugin as my sole backup method, but I need some assurance that it’s working properly and these failed messages scare me.

Mar 23 @ 2:02:41 am	A total of 12MB of memory was used to complete this backup.	
Mar 23 @ 2:02:41 am	A total of 14 files were processed.	
Mar 23 @ 2:02:41 am	Total time taken to complete the full backup process is 151 secs.	
Mar 23 @ 2:02:41 am	Backup complete.	
Mar 23 @ 2:02:40 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:33 am	Resuming backup.	
Mar 23 @ 2:02:31 am	Preparing for next call from server.	
Mar 23 @ 2:02:27 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:26 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:25 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:25 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:24 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:24 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:24 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:16 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:16 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:15 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:13 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:10 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:02:09 am	Resuming backup.	
Mar 23 @ 2:01:57 am	Preparing for next call from server.	
Mar 23 @ 2:01:56 am	Preparing for next call from server.	
Mar 23 @ 2:01:53 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:53 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:52 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:52 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:50 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:49 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:49 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:48 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:36 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:35 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:34 am	Resuming backup.	
Mar 23 @ 2:01:33 am	Resuming backup.	
Mar 23 @ 2:01:22 am	Preparing for next call from server.	
Mar 23 @ 2:01:13 am	Failed to parse Content-Range header- (400)	
Mar 23 @ 2:01:13 am	Ending File List Iterator.	
Mar 23 @ 2:01:06 am	Starting File List Iterator.	
Mar 23 @ 2:01:06 am	SQL backup complete. Starting file backup.	
Mar 23 @ 2:01:01 am	Starting SQL backup.	
Mar 23 @ 2:01:01 am	Resuming backup.	
Mar 23 @ 2:00:10 am	Your time limit is 120 seconds and your memory limit is 768M	
Mar 23 @ 2:00:10 am	Connected Repo is g_drive.	
Mar 23 @ 2:00:10 am	Backup started on Thursday March 23, 2017.