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" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: HTTP with Simple Components: Status.Kind always File
Date: Fri, 21 Jul 2017 09:14:18 +0200
Organization: Aioe.org NNTP Server
Message-ID: <oks9ka$hao$2@gioia.aioe.org>
References: <2017071720305687401-contact@flyx.org>
 <okj8fj$8ue$1@gioia.aioe.org> <2017071918093536089-contact@flyx.org>
 <oko1kk$1pf7$1@gioia.aioe.org> <2017071923134489971-contact@flyx.org>
 <okprak$fmq$1@gioia.aioe.org> <2017072015354641511-contact@flyx.org>
 <lyh8y6n96n.fsf@pushface.org> <okr5ft$vpp$1@gioia.aioe.org>
 <2017072023125178180-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: 8bit
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:47484
Date: 2017-07-21T09:14:18+02:00
List-Id: <comp.lang.ada>

On 20/07/2017 23:12, Felix Krause wrote:
> On 2017-07-20 20:57:35 +0000, Dmitry A. Kazakov said:
> 
>> On 2017-07-20 22:29, Simon Wright wrote:
>>>
>>> The RFC that Dmitri quotes is for URIs. You want the one that defines
>>> the HTTP protocol, currently RFC7230 - see section 3, Message Format.
>>> https://tools.ietf.org/html/rfc7230#section-3
> 
> Ah, I looked at an older RFC for HTTP 1.1; I wasn't aware there was a newer
> one. This newer one indeed defines query as part of the request target:
> 
>     https://tools.ietf.org/html/rfc7230#section-5.3
> 
>     request-target = origin-form
>                     / absolute-form
>                     / authority-form
>                     / asterisk-form
>     origin-form    = absolute-path [ "?" query ]
>>
>> So, is it OK to always recognize query part in the path. Correct?
> 
> Yes, although to avoid confusion, it may be a good idea to not name
> it „Path“. Reading the spec, „Origin“ might be more appropriate. But
> I guess that change would break backwards compatibility.

I think I will just move the Query member out of the variant choice like 
this:

    type Status_Line
         (  Kind         : Status_Line_Type;
            Path_Length  : Natural;
            Host_Length  : Natural;
            Query_Length : Natural
         )  is
    record
       Query : String (1..Query_Length);
       case Kind is
          when None =>
             null;
          when File =>
             File : String (1..Path_Length);
          when URI =>
             Scheme : Scheme_Type;
             Host   : String (1..Host_Length);
             Port   : Port_Type;
             Path   : String (1..Path_Length);
       end case;
    end record;

That should keep it backward compatible.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de