|
Posted by Peter on 12/29/06 20:04
Well I'll be ....
You're right, the data is there !!
And I now was able to fix the problem as well.
There was a small flaw in the script but when I started debugging it I
always passed the data via the URL (GET) instead of going though the pages
using POST.
Via the URL the data after the # was clearly gone so I figured that was the
issue without realising that this may be different for POST !
However, via POST the string is intact and a small fix in the script now
deals with the data correctly.
Thanks for the tip.
-------------------------------------------------------
"Michael Fesser" <netizen@gmx.de> wrote in message
news:dgiap2l8kbcp05a7kr648idunbpgholbq3@4ax.com...
> .oO(Peter)
>
>>I take it the silence means there is no solution ?
>
> IMHO there's not even a problem, or I just don't see it.
>
> Because the # is a reserved character in a URL, every browser will
> automatically URL-encode it to %23 before submitting the form. I would
> say there's something wrong in your receiving script. What does a
>
> var_dump($_POST);
>
> at the beginning of your receiving script show, when you enter something
> with an octothorpe in your form?
>
> Micha
>
Navigation:
[Reply to this message]
|