From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: HTTP with Simple Components: Status.Kind always File Date: Thu, 20 Jul 2017 15:57:54 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <2017071720305687401-contact@flyx.org> <2017071918093536089-contact@flyx.org> <2017071923134489971-contact@flyx.org> <2017072015354641511-contact@flyx.org> NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:47466 Date: 2017-07-20T15:57:54+02:00 List-Id: On 20/07/2017 15:35, Felix Krause wrote: > My suggestion is thus to parse the query even if you get a path. As I > see it, this will not directly > violate the spec. HTTP defines that: > > Servers SHOULD respond to invalid Request-URIs with an appropriate > status code. > > If a path contains a '?', it is an invalid Request-URI. The SHOULD > allows you to handle this differently without violating the spec. > > I look forward to your opinion. How about this. I could add a Boolean parameter to control the behavior: 1. If False everything is as it is now; 2. If True and the path contains either '?' or '#' (something else?), it is parsed as if HTTP_Scheme was there. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de