| 1 | | The reason I'm setting 'Content-Length' to an incorrect value is purely for the purposes of reproducing the issue. The issue itself can occur under different and more complicated circumstances in a production environment with the 'Content-Length' set to a correct value. Why? If the POST body is bigger and sent as multiple packets, and the typical MTU is 1,500 bytes, then there other reasons why some of those packets can get delayed for (longer) periods of time, thus triggering the upstream timeout. |
| | 1 | The reason I'm setting 'Content-Length' to an incorrect value is purely for the purposes of reproducing the issue. |
| | 2 | |
| | 3 | The issue itself can occur under different / more complicated circumstances in a production environment with the 'Content-Length' set to a correct value. Why? If the POST body is bigger and sent as multiple packets, and the typical MTU is 1,500 bytes, then there other reasons why some of those packets can get delayed for (longer) periods of time, thus triggering the upstream timeout. |
