Version `3.0.3` inserts two spaces in the HTTP call and results in `400 BAD_REQUEST` response

[tute]

$ siege -v
SIEGE 3.0.3

$ siege -g -c1 -b -r1 -v "http://example.com/ POST"
POST /  HTTP/1.0
Host: example.com
Accept: */*
User-Agent: JoeDog/1.00 [en] (X11; I; Siege 3.0.3)

HTTP/1.1 400 BAD_REQUEST

$ telnet example.com 80
GET / HTTP/1.0
Host: example.com
User-Agent: JoeDog/1.00 [en] (X11; I; Siege 3.0.3)

HTTP/1.1 301 Moved Permanently

$ telnet example.com 80
GET /  HTTP/1.0
Host: example.com
User-Agent: JoeDog/1.00 [en] (X11; I; Siege 3.0.3)

HTTP/1.1 400 BAD_REQUEST

When GET / HTTP/1.0 has two spaces instead of 1 (GET / HTTP/1.0) our server responds with 400, and we couldn't find a way to make it work more than backporting to version 3.0.0. Not sure if it's a bug on siege or in how our servers (in EC2) interpret HTTP.