iPXE currently checks that the server has not closed the connection mid-stream (i.e. in the middle of a chunked transfer, or before the specified Content-Length has been received), but does not check that the server got as far as starting to send data. Consequently, if the server closes the connection before any data is transferred (e.g. if the server gives up waiting while iPXE performs the validation steps for TLS), then iPXE will treat this as a successful transfer of a zero-length file. Fix by checking the RX connection state, and forcing an error if the server has closed the connection at an unexpected point. Originally-fixed-by: Marin Hannache <mareo@mareo.fr> Signed-off-by: Michael Brown <mcb30@ipxe.org>tags/v1.20.1
|
|
||
60 |
|
60 |
|
61 |
|
61 |
|
62 |
|
62 |
|
63 |
|
|
|
64 |
|
|
|
65 |
|
|
|
66 |
|
63 |
|
67 |
|
64 |
|
68 |
|
65 |
|
|
|
||
111 |
|
108 |
|
112 |
|
109 |
|
113 |
|
110 |
|
|
111 |
|
|
|
112 |
|
|
|
113 |
|
|
|
114 |
|
|
114 |
|
115 |
|
|
116 |
|
|
|
117 |
|
|
|
118 |
|
|
115 |
|
119 |
|
116 |
|
120 |
|
117 |
|
121 |
|
|
|
||
251 |
|
255 |
|
252 |
|
256 |
|
253 |
|
257 |
|
254 |
|
|
|
255 |
|
|
|
256 |
|
|
|
257 |
|
|
|
|
258 |
|
|
|
259 |
|
|
|
260 |
|
|
|
261 |
|
|
|
262 |
|
|
|
263 |
|
|
|
264 |
|
|
|
265 |
|
|
258 |
|
266 |
|
259 |
|
267 |
|
260 |
|
268 |
|