Re: HTTP with Simple Components: Status.Kind always File

[Felix Krause <contact@flyx.org>]

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.

> 
> What is the scheme by default? http? None?

There is no scheme in the origin-form. I would keep this separated from the
full URI and just supply Path and Query in the record.