Skip to main content
Answer

SharePoint File Extractor - 'Too much data for declared Content-Length'

  • June 11, 2025
  • 5 replies
  • 53 views

ShaikhZuber
Committed
Forum|alt.badge.img+1

I am getting following error when ingesting files from SharePoint site to CDF. 

send_request_body.failed exception=LocalProtocolError('Too much data for declared Content-Length')

Anything I need to specify in .yaml file to allow content-length? Also how do I trace which file is causing the problem. I changed Logger to DEBUG level but still don’t see the file name info.

Thanks,

Zuber

Best answer by Mithila Jayalath

@ShaikhZuber can you please upgrade the extractor to the latest version and check again? There was a fix for this issue in Version 2.7.2.

5 replies

Mithila Jayalath
Seasoned Practitioner
Forum|alt.badge.img+8

@ShaikhZuber can you please let me know the extractor version that you are currently using?


ShaikhZuber
Committed
Forum|alt.badge.img+1
  • Author
  • Committed
  • June 12, 2025

file-extractor-standalone-2.6.1-win32.exe


Mithila Jayalath
Seasoned Practitioner
Forum|alt.badge.img+8
  • Seasoned Practitioner
  • Answer
  • June 12, 2025

@ShaikhZuber can you please upgrade the extractor to the latest version and check again? There was a fix for this issue in Version 2.7.2.


Forum|alt.badge.img

AFICT, this doesn’t seem to be an extractor problem. And it’s not something the extractor’s config file sets / configures (nor something you can configure).

According to the source file for the library raising this exception, it is raised when the total amount of sent data fails to match the content-length header value.

Is this a one-time failure, or is it consistent for the file being extracted? 


ShaikhZuber
Committed
Forum|alt.badge.img+1
  • Author
  • Committed
  • June 12, 2025

@Mithila Jayalath  Thanks for the information. Actually, I upgraded extractor to very latest version “file-extractor-standalone-2.9.0-win32” and no errors are coming now. 

@Thomas Sjølshagen  Yes, the error was consistent on each run. Seem they added some fix for it in latest version.