URL encoded '/' characters are unencoded back to slash about sttp

[adamw]

Yes, this is the correct behavior, RFC3986 doesn't require encoding / in the query, as the path is finished by the first occurence of ? (see seciton 3.4)

If you do want to add a parameter with / encoded, you can add a KeyValue(k, v, QueryFragmentEncoding.All) query fragment using the uri.queryFragment method. See https://github.com/softwaremill/sttp/blob/master/core/src/main/scala/com/softwaremill/sttp/Uri.scala#L136-L145 for the full logic

As for de-coding the java.net.URI, that's also correct, as all components are stored in the Uri instance in an un-encoded form, hence they are being URL-decoded when decomposing the java.net.URI.

[hairylime]

thanks, that all makes sense.

The workaround you give almost works, except that the java URI encoder encodes spaces with +, and the (admittedly horrible) 3rd party api I'm trying to hit doesn't like those.

[adamw]

Hmm I don't think it's currently possible to encode space in query other than +. A possible work around would be to add QueryFragmentEncoding.None and then you could do:

uri"http://notahost.com".queryFragment(QueryFragment.KeyValue("query", "a%20b", valueEncoding = QueryFragmentEncoding.None))

what do you think?

[adamw]

Fixed in 2.0.0-M6: URI encoding is fully configurable