~ overflow ~

You might be wondering why someone would send encoded data to php to be inserted on a table, just think that you need to put a html into a table, how many issues you can fall into? it’s much easier encode it, so then you fall into a different issue…

i’m using a regular base64 encode/decoder script wich you can find by searching google “javascript base64″;

the problem is that once you send the base64 data to php by POST or GET it gets corrupted! why this happens? cuz life sucks?!

so i figured out a interesting thing

base64 uses the character “+” wich is the same character to determine spaces on the POST/GET data, so basically when you send information by a form it will be sent like this:

“bleh bleh bleh” -> “bleh+bleh+bleh” when php gets it it will convert back to the original string (replacing the “+”’s with ” ” (space)) that made the javascript base64’s encoded information to get corrupted, just like this:

original base64 encode:

PGh0bWw+PGhlYWQ+PHRpdGxlPl

after sending to php it will be added as this on the database:

PGh0bWw PGhlYWQ PHRpdGxlPl

so to fix this issue, you just need a str_replace(" ","+",$base64_data_from_javascript) to fix it.

that’s all.