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!border1.nntp.ams1.giganews.com!border2.nntp.ams1.giganews.com!nntp.giganews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer01.fr7!futter-mich.highwinds-media.com!news.highwinds-media.com!fx43.am4.POSTED!not-for-mail
From: Felix Krause <contact@flyx.org>
Newsgroups: comp.lang.ada
Message-ID: <2017071923134489971-contact@flyx.org>
References: <2017071720305687401-contact@flyx.org>
 <okj8fj$8ue$1@gioia.aioe.org> <2017071918093536089-contact@flyx.org>
 <oko1kk$1pf7$1@gioia.aioe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: HTTP with Simple Components: Status.Kind always File
User-Agent: Unison/2.2
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Wed, 19 Jul 2017 21:12:23 UTC
Organization: Eweka Internet Services
Date: Wed, 19 Jul 2017 23:13:44 +0200
X-Received-Bytes: 2167
X-Received-Body-CRC: 2483321626
X-Original-Bytes: 2116
Xref: news.eternal-september.org comp.lang.ada:47455
Date: 2017-07-19T23:13:44+02:00
List-Id: <comp.lang.ada>

On 2017-07-19 16:33:15 +0000, Dmitry A. Kazakov said:

> On 2017-07-19 18:09, Felix Krause wrote:
>> 
>> Well, this is the behavior I expect, but I *am* querying the server 
>> with an URI containing a schema.
> 
> How do you know? How exactly looks the request? If you don't trust the 
> integrated trace you can use Wireshark to be sure.

I enabled the internal trace and in fact, there is no schema on the 
incoming GET.

> I must see what is sent from the client in order to tell if it is a bug 
> or correct behavior. A command line tells nothing.

In my view, it is not correct behavior that Status.Kind is File when 
the request has been sent via HTTP, regardless of whether the schema is 
part of GET URI or not. As I explained earlier, for a File, I only get 
the Path string. I cannot parse this properly since HTTP server already 
unescaped the escaping sequences. Let me give an example:

    curl "http://localhost:8088/foo?key=value"

    curl "http://localhost:8088/foo%3Fkey=value"

The first command should fetch a resource with the path `/foo` and the 
query `?key=value`. The second command should fetch a resource with the 
path `/foo?key=value`. However, I do not see the difference in the Path 
string I get from the HTTP server, which makes me unable to 
differentiate between those two cases. Thus, the HTTP server should 
give me an URI instead, even if the path on the GET line does not 
contain a scheme.