id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	difficulty
1074	intarweb request parsing and  Spiffy handling of said requests is inconsistent in case of improper request line URIs	RvdH	sjamaan	"Not sure in which egg the actual bug is residing, but sometimes the server closes the connection instead of returning a 400: Bad Request

You can simulate a Bad Request by starting Spiffy and requesting {{{http://127.0.0.1:8080//}}}. Requesting a double slash returns a 400. (Whether that is a valid 400 or not is open for debate.)

But requesting the following URLs closes the connection, without returning anything:
* http://127.0.0.1:8080/%
* http://127.0.0.1:8080//%20/
* http://127.0.0.1:8080//""
* http://127.0.0.1:8080/%""
* http://127.0.0.1:8080//%%20/

"" is actually %22, so I think the problem lies somewhere with handling %-characters.
"	defect	closed	major	someday	unknown	4.8.x	fixed	bad-request connection	andyjpb@…