Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The content of a response is not return on 413

See original GitHub issue

When trying to post through Google Load Balancer I get this error and the response it not returned from the Nginx but the curl version works.

$ http -f POST XXX \
> variables='XXXX' \
> file@./testfile.dat
http: error: ConnectionError: ('Connection aborted.', BrokenPipeError(32, 'Broken pipe')) while doing POST request to URL: XXXX

$ curl -v XXXX \
> -H "Content-Type:multipart/form-data" \
> -F XXXX
> -F 'file=@./testfile.dat'
*   Trying XXXX...
* TCP_NODELAY set
* Connected to XXXX (XXXX) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: XXX
* Server certificate: RapidSSL SHA256 CA
* Server certificate: GeoTrust Global CA
> POST /api/graphql HTTP/1.1
> Host: XXX
> User-Agent: curl/7.51.0
> Accept: */*
> Content-Length: 104858299
> Expect: 100-continue
> Content-Type:multipart/form-data; boundary=------------------------200e4faa1c52a317
>
< HTTP/1.1 413 Request Entity Too Large
< Server: nginx/1.13.3
< Date: Wed, 09 Aug 2017 12:12:02 GMT
< Content-Type: text/html
< Content-Length: 199
< Strict-Transport-Security: max-age=15724800; includeSubDomains;
< Via: 1.1 google
< Alt-Svc: clear
< Connection: close
<
<html>
<head><title>413 Request Entity Too Large</title></head>
<body bgcolor="white">
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.13.3</center>
</body>
</html>
* Curl_http_done: called premature == 0
* Closing connection 0

Issue Analytics

State:
Created 6 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

kevinsimpercommented, Sep 1, 2018

@jakubroztocil It kind of have, since Connection aborted is showed from httpie and not from curl. @redalert11 It is not nginx that is the problem, it is that curl shows the correct output and httpie doesn’t with the same input 😃

0reactions

redalert11commented, Sep 1, 2018

opps… @kevinsimper. i meant to post this somewhere else. 😛