I thought the cookie would be used too, but it seems to be replaced on
each http call to the server. Take a look at the url for Worldpay:

https://select.worldpay.com/wcc/purchase

When you first load it a cookie is set. The error you see is expected
because normally POST information is sent. If you reload the screen you
get a server error. From my tests, this is because it matches the cookie
on your machine with something it expects, and fails. Its hard to see
this just on this example, but when i send real data to it via the
browser, and use liveheaders to track, i see new cookies, for the same
variable, being set on each return from the system.

If curl isn't able to move the user to the POST location, like a browser
does, is there a way to mimick this? How does a browser do this?

Many thanks,

Paul
Received on 2004-03-10