[snip]
I don't think cURL is the right weapon to keep form/content separate
from processing...
[/snip]
It may not be, but it was a thought. As they say, there is more than one way
to skin a cat. In this case I was hoping to save a trip to a database or
flat file so that the URL wouldn't have to be
On Tue, October 25, 2005 11:40 am, Jay Blanchard wrote:
> [snip]
> If you want their browser to surf there, you have to send "Location: "
> headers, and you'd need to include whatever GET parameters you could
> to make the request come out like you want, but, at that point,
> there's not much reaso
[snip]
If you want their browser to surf there, you have to send "Location: "
headers, and you'd need to include whatever GET parameters you could
to make the request come out like you want, but, at that point,
there's not much reason for cURL to be involved...
[/snip]
I wanted to avoid using GET
On Tue, October 25, 2005 8:36 am, Jay Blanchard wrote:
> I am trying a new technique, for me, when processing a form. The form
> is
> filled out and submitted, during processing it is determined that
> there is
> an error with the posted data...such as a blank or mismatched
> password,
> I want to
4 matches
Mail list logo
