junkyardog55
New Member
I have an encrypted, base64 encoded array that I need to put into a url and insert into emails we send to clients to enable them to be identified (uniquely) - the problem is that base64_encode() often appends an = symbol or two after it's string of characters, which by default is disallowed by CI.Here's an example:http://example.com/cec/pay_invoice/...XMllEWlZaaEFHeFJZMU51VVdNTmJsdzNWVzlVT0EwZw==Now I understand I can allow the = sign in config.php, but I don't fully understand the security implications in doing so (it must have been disabled for a reason right?)Does anyone know why it might be a bad idea to allow the = symbol in URLs?Thanks!John.