On 27/01/15 10:40, Yasuo Ohgaki wrote:
> I suppose RFC 1738 user is using urldecode() as rawurldecodoe() cannot
> decode '+'. So you and your users wouldn't have BC issues.
>
> Please let me know if I'm missing something.
It's one of those check boxes on my crib sheet for converting legacy
sites
Hi Lester,
On Tue, Jan 27, 2015 at 6:19 PM, Lester Caine wrote:
> On 27/01/15 02:06, Yasuo Ohgaki wrote:
> > Another example is http_build_query(). It should escape ' ' as '%20' by
> > default, not '+'.
>
> The quick response is probably 'why', but I probably know the answer,
> becuase some stan
On 27/01/15 02:06, Yasuo Ohgaki wrote:
> Another example is http_build_query(). It should escape ' ' as '%20' by
> default, not '+'.
The quick response is probably 'why', but I probably know the answer,
becuase some standard has changed. The problem with this one is that
using a '+' sign when enco
Hi all,
I would like to write RFC that sets appropriate/better defaults by default.
For example, htmlspecialchars has following definition now.
string htmlspecialchars ( string $string [, int $flags = ENT_COMPAT |
ENT_HTML401 [, string $encoding = ini_get("default_charset") [, bool
$double_encod
