OK, I want to send someone back from paypal to a thank you page;
this reloads to the actual file they will purchase. BUT, I want to
include a magic cookie that will prevent someone else from going to
that url at a later time and getting the payload without paying for
it. Any thoughts on how to
On Jul 3, 2011, at 10:58 AM, Kirk Bailey wrote:
OK, I want to send someone back from paypal to a thank you page;
this reloads to the actual file they will purchase. BUT, I want to
include a magic cookie that will prevent someone else from going to
that url at a later time and getting the p
Hello All,
Just so you know, this is not something I made up myself.
It was taken from an online HTML email tutorial.
Also, It has worked for years with no problem and I would still use it,
however I found out about the PHP_EOL and was just curious as to the
difference.
Thanks viraj...
Best,
On Sun, Jul 3, 2011 at 10:31 PM, Karl DeSaulniers wrote:
> Hello All,
> Just so you know, this is not something I made up myself.
> It was taken from an online HTML email tutorial.
> Also, It has worked for years with no problem and I would still use it,
> however I found out about the PHP_EOL and
@Stuart,
Actually that is what made me look into the PHP_EOL Stuart. Wanting
to do things right.
Did you not read my initial email? I am not suggesting anyone adopt
my code.
The question was directed to what the differences are so I COULD
learn the right way.
Being that this was something I
On Sun, Jul 3, 2011 at 11:22 PM, Karl DeSaulniers wrote:
> @Stuart,
> Actually that is what made me look into the PHP_EOL Stuart. Wanting to do
> things right.
> Did you not read my initial email? I am not suggesting anyone adopt my
> code.
> The question was directed to what the differences are s
I see. Yes, I was referring to the PHP manual.
I will investigate the RFC manuals as well like you had noted.
No offense taken. Thank you for the clarification.
Best,
Karl
On Jul 3, 2011, at 6:07 PM, Stuart Dallas wrote:
On Sun, Jul 3, 2011 at 11:22 PM, Karl DeSaulniers
wrote:
@Stuart,
Act
Hello Stuart,
After some closer look at the RFC Compliant manuals you suggested,
I have determined that the creator of that code was in fact RFC821
Compliant.
Being that this was a code I found several years ago, RFC822 may not
have been in effect.
This being the reason (I believe) that the cr
