Questions on INPUT behavior

[Jason McBrayer]

solderpunk writes:
>> > 5. In the above example, what happens if a request to that URL
>> > returns a status code of 10? Should the client strip the existing
>> > query components from the URL, or append a new key=value pair to
>> > the end?
>
> Hmm. If a client requests the URL above, it should include the query
> string in the request. So why would the server respond with a status
> 10 in that case? I mean, it's currently not prohibited in the spec for
> a server to do that, so this is a fair question. I'm not sure whether
> we *should* forbid it or spec some sensible client response. Did you
> have a use case in mind or are you just keeping an eye out for edge
> cases?

I can imagine a client asking successive questions in response to
answers. But I'm not sure what the client should do. We might want to
specify that Gemini URLs should not contain query parts except in
requests initiated by 1x responses. Or that the query part should never
be significant in a published URL; that it should be a pre-filled
suggestion that can be modified by the client.

--
Jason McBrayer      | “Strange is the night where black stars rise,
jmcbray at carcosa.net | and strange moons circle through the skies,
                    | but stranger still is lost Carcosa.”
                    | ― Robert W. Chambers,The King in Yellow