Open fnimick opened 6 months ago
I think this is intended behaviour. See https://stackoverflow.com/questions/940905/can-i-read-the-hash-portion-of-the-url-on-my-server-side-application-php-ruby
You're right, this is mostly shopify being silly - they explicitly send a urlencoded #
character in their queries to your service endpoint. https://shopify.dev/docs/apps/fulfillment/fulfillment-service-apps/manage-fulfillments#step-8-optional-enable-tracking-support
Their example URL: http://myapp.com/fetch_tracking_numbers.json?order_names[]=#1001.1&order_names[]=#1002.1&order_names[]=#1003.2&shop=testshop.myshopify.com×tamp=1669900140
A question (not a bug, but a potential feature) is, would it be worth allowing httpie to support urlencoding illegal characters in cases such as these where we have to simulate requests that are being made that use the #
character in the url?
Checklist
Minimal reproduction code and steps
Observe that the full argument string is being sent from the shell (as visible in debug mode)
However, when the URL is displayed in verbose mode, the URL is truncated at the first hash mark. (And the server logs confirm that the request URL is truncated).
Current result
The query string is truncated at the first hash character. …
Expected result
The full query string is sent to the server.