unexpected EOF - couldnt read request body

Nobody has claimed this yet.

**Describe the bug**
When the orchestrator gets the segment it doesnt transcode, instead it shows the error

`l0114 16:46:50.136605 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/480p0/3.ts
I0114 16:46:50.136605 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/240p0/3.ts
I0114 16:46:50.137117 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/360p0/3.ts`

`I0114 16:46:50.190671 4560 segment_rpc.go:95] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Received segment dur=1.6s`

`I0114 16:46:50.190671 4560 census.go:1055] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentEmerged... duration=1.6`

`E0114 16:46:50.476482 4560 segment_rpc.go:129] manifestID=0777scz7psr051nu seqNo=5 orchSessionID=c3ce2d94 Could not read request body - err="unexpected EOF"`

`I0114 16:46:50.707621 4560 segment_rpc.go:135] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Downloaded segment dur=516.4441ms`

`I0114 16:46:50.707621 4560 census.go:1110] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentDownloaded... dur=516.4441ms`

`I0114 16:46:50.709782 4560 orchestrator.go:483] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Starting to transcode segment`

`I0114 16:46:50.709782 4560 orchestrator.go:492] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Submitted segment to transcode loop`

`I0114 16:46:50.710300 4560 lb.go:60] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 LB: Using existing transcode session for key=c3ce2d94_0`
`...`
`I0114 16:46:50.823788 4560 orchestrator.go:575] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Transcoding of segment took=113.4876ms`

`I0114 16:46:50.823788 4560 census.go:1197] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentTranscode nonce=0 seqNo=4 dur=113.4876ms trusted=true verified=true`

**To Reproduce**
Steps to reproduce the behavior:
I have the portforwarding such that the traffic is redirected from a server in singapore to my orchestrator in another location using VPN

**Expected behavior**
No such error

**Desktop (please complete the following information):**
- Orchestrator - Windows
- Traffic forwading server - Linux
- livepeer version - Latest

Start with segment_rpc.go around the logged errors at lines 95-135 and trace how the segment request body is received before the orchestrator transcodes it. Reproduce the failure using the described VPN and port-forwarding setup, then verify that the request completes without an unexpected EOF and the segment is transcoded successfully.

Written by the indexing model from the issue text.