During testing of another bug, it was found that we have an unequal number of encode/decode cycles in libprocess. This meant that, when given a query such as ?path=C%3A%5Cfoo%5Cbar%253Abaz, it would erroneously go over the wire as C:\\foo
bar%3Abaz, and then once decoded on the other end, it would look for C:\\foo
bar:baz even though the query was trying to express the literal value C:\\foo
Essentially, we were missing an encode in http::internal::encode(Request).