as you can see the problem is with the web server, that does not return a cookie (by means of the Set-Cookie header) to wget.

Yes, that's exactly the problem. Logging on with a standard browser *does* return a cookie and successfully logs you on.

Trying the same with wget, the server does *not* return a cookie, but instead returns message "Your browser cookies couldn't be recognized." in the downloaded HTML.

Two questions:

1. Is there a way to trace the browser traffic and compare that to the wget traffic, to see where they differ.

2. Do you have a working wget example for any publicly accessible server, which uses POST and successfully returns a cookie?

Thanks!

Reply via email to