urlencode() has the particularity of encoding spaces to +, which will get correctly decoded in some contexts but not others (e.g. cookies). I don't remember any case where %20 got rejected where a + wouldn't have been, so I assume this is a safe change and this doesn't require introducing a new encoder.
Patch is ready on my side but I just wanted to make sure I was not missing anything before opening the PR.
How would you feel about changing
urlencode()
torawurlencode()
in both theurl
andsoft
encoders?https://github.com/ambionics/phpggc/blob/6ab7c1477bb4b355076da10dc9ddad66aae3f3be/lib/PHPGGC.php#L434-L436
https://github.com/ambionics/phpggc/blob/6ab7c1477bb4b355076da10dc9ddad66aae3f3be/lib/PHPGGC.php#L437-L440
urlencode()
has the particularity of encoding spaces to+
, which will get correctly decoded in some contexts but not others (e.g. cookies). I don't remember any case where%20
got rejected where a+
wouldn't have been, so I assume this is a safe change and this doesn't require introducing a new encoder.Patch is ready on my side but I just wanted to make sure I was not missing anything before opening the PR.