And hello @trezm again o/
It seems that Thruster always appends its own headers :
Content-Lengthmay not be set with the header
Transfer-Encoding: chunked. See https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4 (Third bullet point). But apparently the
Content-Length "MUST be ignored" (by the receiver) if
Transfer-Encoding is present. How do you understand this?
If a Content-Length header field (section 14.13) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. And I'm not sure if Thruster considers only the length of the chunk.
cargo run --example <example name>, so in this case
cargo run --example most_basic
cargo run --example hello_world
App::createaccepts a function. A closure is not possibile.
GETqueries where the same parameter appears multiple times, in order to pass a list of values for that parameter.
context.query_params, but as this is a hash map,
varonly gets one value, the last one.
request.path, is there a way to retrieve that as a vector or some kind of collection per parameter?