Why are you doing it this way? RFC 3389 clearly specifies path encoding rules for such cases: https://www.rfc-editor.org/rfc/rfc3986.html#section-3.3   Every properly implemented client will support this. And every competently implemented server code will aswell.   Specifically, your example sku :/?#[]@&*+; will yield the uri path /api/v1/inventory/:%2F%3F%23%5B%5D@&*+; according to rfc3986 3.3. ... View more