J
Joerg Jooss
Thus wrote macro,
Another user mentioned this behaviour a couple of weeks ago :-/
Deleting the cookie from the container manually should work.
Cheers,
when I use HttpWebRequest with CookieContainer object that handles
cookies, i make more than one request and needs to handle cookies
being added and removed between requests, just like a regular web
browser like internet explorer.
if I have this cookie header in a response:
Set-Cookie: <CookieName>=; path=/;expires=01-Jan-1999 00:00:00 GMT
the cookie is not deleted for the next request, and is being sent
again with the old value, while should be deleted - and actually is
deleted with Internet Explorer as client.
is this a bug is there a solution / workaround by manually deleting
the cookie?
Another user mentioned this behaviour a couple of weeks ago :-/
Deleting the cookie from the container manually should work.
Cheers,