Pages: 1 2
Am 20.10.2013 00:01, schrieb mike:
Yeah, I don't think the encoder is converting all the data from the image to base64. I went to a site that converts images to base64, and I compared that to what i got from mime64.data and there seems to be some null characters within it. I can show you the two files if you need to see something.
Two example files as a test case would be great, as the little random
data unit test works fine.
Here is the base64 URL data
http://pastebin.com/3DyYQFyc
Here is what vibe.d base64 gives me (I made a slight change of removing /r/n because it isn't valid for base64 URL)
http://pastebin.com/AEjiGWxw
Pastebin stops when it reaches the null characters, there is more information from the vibe.d base64 version though. I can upload a file containing the data somewhere if you need me to.
I'm on Opensuse and I'm using a tool (Diff viewer) to compare. The vibe.d version matches exactly until it gets to the null characters, which explains why Redis was missing data. (Redis is awesome!)
Am 22.10.2013 01:41, schrieb Mike:
Here is the base64 URL data
http://pastebin.com/3DyYQFycHere is what vibe.d base64 gives me (I made a slight change of removing /r/n because it isn't valid for base64 URL)
http://pastebin.com/AEjiGWxwPastebin stops when it reaches the null characters, there is more information from the vibe.d base64 version though. I can upload a file containing the data somewhere if you need me to.
I'm on Opensuse and I'm using a tool (Diff viewer) to compare. The vibe.d version matches exactly until it gets to the null characters, which explains why Redis was missing data. (Redis is awesome!)
Thanks. I'll try to reproduce the null characters, no need to jump
through hoops to get the result pasted.
Pages: 1 2
