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

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 19/07/2017 23:13, Felix Krause wrote:
> 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.

See, there is no bug so far.

>> 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.

Well, it processes what the client sends.

> 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"

I see, you want to the recognize the query part (and possibly the 
fragment part) even when no scheme present.

I think what you want is illegal. I might be wrong, people claim ARM is 
complicated, they should read RFCs!

Anyway, my interpretation of RFC 3986 is that the scheme part must be 
present:

    https://tools.ietf.org/html/rfc3986#section-1.1.1

No scheme, no query part. Therefore in both

    GET /foo?key=value
    GET foo%3Fkey=value

"foo?key=value" must be the path.

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