[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #1074: [intarweb/spiffy] Connection closed on "Bad Re
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #1074: [intarweb/spiffy] Connection closed on "Bad Request" with %-character |
Date: |
Fri, 22 Nov 2013 23:21:51 -0000 |
#1074: [intarweb/spiffy] Connection closed on "Bad Request" with %-character
------------------------------------+---------------------------------------
Reporter: RvdH | Owner: sjamaan
Type: defect | Status: new
Priority: major | Milestone: someday
Component: unknown | Version: 4.8.x
Keywords: bad-request connection |
------------------------------------+---------------------------------------
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.
--
Ticket URL: <http://bugs.call-cc.org/ticket/1074>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
- [Chicken-janitors] #1074: [intarweb/spiffy] Connection closed on "Bad Request" with %-character,
Chicken Trac <=
- Re: [Chicken-janitors] #1074: uri-generic: percent-encodings in the authority section cause problems (was: [intarweb/spiffy] Connection closed on "Bad Request" with %-character), Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: uri-generic: percent-encodings in the authority section cause problems, Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is invalid in case of improper request line URIs (was: uri-generic: percent-encodings in the authority section cause problems), Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs (was: intarweb request parsing and Spiffy handling of said requests is invalid in case of improper request line URIs), Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/23
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/24
- Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs, Chicken Trac, 2013/11/24