[snip]
If the form is submitted from a web browser, the POSTed data IS
available/visible (print_r) in the new web page.
If the form--that is, any form--is submitted from an email client
(any email client), the POSTed data IS NOT available/visible in the
new web page.
So... I can think of thr
On 20-Mar-06, at 4:40 PM, Richard Lynch wrote:
On Mon, March 20, 2006 5:04 pm, René Fournier wrote:
What does this value actually look like?
How long is it?
Is mail wrapping it to 72 characters with a newline, thereby breaking
the data up?
Though you would still get some POST data, just n
On Mon, March 20, 2006 5:04 pm, René Fournier wrote:
> value="serialized and htmlentitized array values..."> type="submit" name="submit" value="Fill">
>
> I've narrowed it down a little farther:
>
> 1. If I copy the form from the email into the destination php page
> ("ProcessSignin.php"), and cli
On 20-Mar-06, at 3:05 PM, Jay Blanchard wrote:
[snip]
Hmm, perhaps I didn't explain clearly. To put it another:
1. A script sends an email to a user with sign-in details.
2. The user clicks a [submit] button in the email message called
"Quick Sign In"
3. A web browsers opens to http://www.websi
#1. Show us the FORM.
#2. Show us the email itself
#3. Show us the code that processes the POST data.
Without that, we're just guessing in the dark.
Can you make the form work on your server, WITHOUT the email involved?
Check your httpd.conf carefully. There is no inherent reason why this
sho
Jay Blanchard wrote:
[snip]
Hmm, perhaps I didn't explain clearly. To put it another:
1. A script sends an email to a user with sign-in details.
2. The user clicks a [submit] button in the email message called
"Quick Sign In"
3. A web browsers opens to http://www.website.com/signin.php (from
[snip]
Hmm, perhaps I didn't explain clearly. To put it another:
1. A script sends an email to a user with sign-in details.
2. The user clicks a [submit] button in the email message called
"Quick Sign In"
3. A web browsers opens to http://www.website.com/signin.php (from
the http://www.website
Hmm, perhaps I didn't explain clearly. To put it another:
1. A script sends an email to a user with sign-in details.
2. The user clicks a [submit] button in the email message called
"Quick Sign In"
3. A web browsers opens to http://www.website.com/signin.php (from
the http://www.website.com/s
[snip]
I have a script that periodically sends an email that includes form
post to a script, which is meant to do something with the posted data.
My problem is that apparently some PHP security measure is not
permitting the externally posted data to be access via $_POST. I
assume this is du
I have a script that periodically sends an email that includes form
post to a script, which is meant to do something with the posted data.
My problem is that apparently some PHP security measure is not
permitting the externally posted data to be access via $_POST. I
assume this is due to c
10 matches
Mail list logo
