Description:
------------
Per RFC2045, section 6.8, base64 decoding should not count line breaks and other whitespace as errors. When using $strict=True, base64_decode() does ignore whitespace, except at the end of any base64 encoded data that ends with padding characters (=). If there is whitespace after the padding character(s), the string is rejected under strict testing. This is incorrect. 

One particular problem with this is that you cannot reliably round-trip base64 encode/decode with strict checking when using chunk_split() on the encoded data, because chunk_split puts a newline at the end of the data. If the length of the original data is a multiple of 3, it works, otherwise it does not. 

Test script:
---------------
<?php
function test($s)
{
  $v = chunk_split(base64_encode($s));
  $r = base64_decode($v, True);
  echo "$s=";
  var_dump($r);
}
test('PHP');
test('PH');
test('P');

Expected result:
----------------
PHP=string(3) "PHP"
PH=string(2) "PH"
P=string(1) "P"


Actual result:
--------------
PHP=string(3) "PHP"
PH=bool(false)
P=bool(false)