On Tue, Feb 21, 2006 at 04:58:01PM -0600, Richard Lynch wrote:
> You'd have to check if URL-encoding supports whatever sort of
> characters/data is your input.
>
> I would *THINK* that URL-encoding standard would support binary data
> of any kind, and be the correct way to do this, in THEORY.
>
>
You'd have to check if URL-encoding supports whatever sort of
characters/data is your input.
I would *THINK* that URL-encoding standard would support binary data
of any kind, and be the correct way to do this, in THEORY.
In PRACTICE, it may be that the implementation of URL-encode would not
corre
Thanks for the info, it was really helpfull. One question though, is
it necessary to first encode my data with the base64 algo, or can I
skip that step and immediately urlencode my data?
Dirk
On 2/21/06, Richard Lynch <[EMAIL PROTECTED]> wrote:
> You probably should be URL-encoding your data in t
You probably should be URL-encoding your data in the first place...
http://php.net/urlencode
http://example.com/$data";
//RIGHT:
$URL = "http://example.com/$data_url";;
If it's not feasible for your C++ application to replicate urlencode()
then you may be able to get what you want with that http
Thanks for the hint, I'm not doing any encoding at the moment, I'll
try it out tomorrow.
Dirk
On 2/21/06, Paul Scott <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-02-21 at 19:40 +0100, Dirk Vanden Boer wrote:
> > The post argument then looks like data=&A
> > Reading the post is done like this:
> > if
On Tue, 2006-02-21 at 19:40 +0100, Dirk Vanden Boer wrote:
> The post argument then looks like data=&A
> Reading the post is done like this:
> if (isset($_POST['data'])
> Is there a way to fix this problem?
>
Have you tried base64_encoding the binary data, then decoding it again
on the PHP side?
6 matches
Mail list logo
