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:15:47 +0200
Organization: Aioe.org NNTP Server
Message-ID: <oks9n3$hao$3@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>
 <lyd18umfp9.fsf@pushface.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:47486
Date: 2017-07-21T09:15:47+02:00
List-Id: <comp.lang.ada>

On 21/07/2017 09:06, Simon Wright wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> 
>>> 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
>>
>> So, is it OK to always recognize query part in the path. Correct?
>>
>> What is the scheme by default? http? None?
> 
> See https://tools.ietf.org/html/rfc7230#section-5.3.1 :
> 
>     For example, a client wishing to retrieve a representation of the
>     resource identified as
> 
>       http://www.example.org/where?q=now
> 
>     directly from the origin server would open (or reuse) a TCP
>     connection to port 80 of the host "www.example.org" and send the
>     lines:
> 
>       GET /where?q=now HTTP/1.1
>       Host: www.example.org
> 
>     followed by the remainder of the request message.

OK, thanks for clarification.

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