Lee James

Hi @rolandwalker, yes they are! Here are the results from the `SELECTs` that you mentioned: ``` ➜ mycli -uroot -ppassword -h127.0.0.1 --database encoding_fun --csv -e 'SELECT 0x446709595B4447CFB62E772B5A32535C' "0x446709595B4447CFB62E772B5A32535C" "Dg Y[DG϶.w+Z2S\"...

@rolandwalker would you please share what happens when you run these? Perhaps that could help identify what is different between our setups

@rolandwalker would you please share what happens when you run these steps? If you are getting something different, it may help to isolate the issue.

Update - I have tracked the issue to Python. The encoding issue occurs when Python performs the conversion from the hex value to bytes ``` >>> bytes.fromhex('E4A82330EF764A4F9E66168B94DE85C9') b'\xe4\xa8#0\xefvJO\x9ef\x16\x8b\x94\xde\x85\xc9' >>> bytes.fromhex('446709595B4447CFB62E772B5A32535C')...

I am also running into this now. I tried the Python Flask app and it works for making a request (with query parameters) directly from the browser (and curl), but...

I managed to fix the CORS issue by rewriting the last line in `app.py` to merge the lambda headers dictionariy with `{'Access-Control-Allow-Origin': '*'}` via the following: ```python return Response(lambda_response['body'], status=lambda_response['statusCode'],...