Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] 413 HTTP response returned when uploading large files via LiveResponse #543

Open
7a6570 opened this issue Oct 29, 2024 · 8 comments
Open

[BUG] 413 HTTP response returned when uploading large files via LiveResponse #543

7a6570 opened this issue Oct 29, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@7a6570
Copy link

7a6570 commented Oct 29, 2024

I am seeing this behaviour on:

  • OS: Linux
  • Carbon Black Cloud Products: Enterprise EDR, Audit & Remediation
  • Python Version: 3.11.2

Describe the bug
When uploading large files to endpoints via LiveResponse, a HTTP 413 response is returned from the backend:

<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body>\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>

Steps to Reproduce

Upload a large file (e.g. 40MB) to an endpoint using the cbc sdk:

with endpoint.lr_session() as lr_session:
  lr_session.put_file(fp, dest_path)

Expected behavior
Until recently, it was possible to upload a 40MB file to clients using the cbc SDK.
@7a6570 7a6570 added the bug Something isn't working label Oct 29, 2024
@7a6570
Copy link
Author

7a6570 commented Nov 6, 2024

I did some additional testing: if the file is smaller than 1MB, the upload still works, otherwise it fails returning the HTTP 413 header.
Uploading the large file (40MB) via browser seems to work though.
Can you please into this issue ? thx

@avanbrunt-cb
Copy link
Contributor

Sorry for the slow response. Your saying this was support previously but has stopped working? Do you know when that stopped working?

@avanbrunt-cb
Copy link
Contributor

What version of the SDK are you using as we attempted a fix for this in 1.5.6 with this PR #533

@7a6570
Copy link
Author

7a6570 commented Nov 19, 2024

Sorry for the slow response. Your saying this was support previously but has stopped working? Do you know when that stopped working?

Yes this worked for a long time and stopped working maybe three or four weeks ago.

What version of the SDK are you using as we attempted a fix for this in 1.5.6 with this PR

I'm using version 1.5.6

@avanbrunt-cb
Copy link
Contributor

@7a6570 Can you open a support case with us and drop the case number here. Nothing has changed in the SDK so this is likely the backend API somewhere

@avanbrunt-cb
Copy link
Contributor

We made one minor change in 1.5.6 with this PR #533

Can you try using 1.5.5 and letting me know if that makes a difference

@avanbrunt-cb
Copy link
Contributor

We have confirmed a backend issue and it is being worked on

@7a6570
Copy link
Author

7a6570 commented Nov 21, 2024

We have confirmed a backend issue and it is being worked on

OK, thanks for the update. I already opened a case, the number is: 35912150

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@7a6570 @avanbrunt-cb