Thanks, But I have a problem. I upgraded to 1.8.1 for win9x. I found the cookie file for netscape 4 and 6 which are different from one another. I made sure that each had the correct cookie set for the website in question. I tried both and got the same error message
*************************** Connecting to www.mapblast.com[165.193.102.140]:80... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://www.mapblast.com/myblast/index.mb [following] --16:09:45-- http://www.mapblast.com/myblast/index.mb => `output' Connecting to www.mapblast.com[165.193.102.140]:80... connected. HTTP request sent, awaiting response... 200 OKSyntax error in Set-Cookie: premat ure end of string. Syntax error in Set-Cookie: premature end of string. Syntax error in Set-Cookie: premature end of string. Syntax error in Set-Cookie: premature end of string. Syntax error in Set-Cookie: premature end of string. Syntax error in Set-Cookie: premature end of string. Length: 18,857 [text/html] 100%[====================================>] 18,857 55.80K/s ETA 00:00 16:09:46 (55.80 KB/s) - `output' saved [18857/18857] FINISHED --16:09:46-- Downloaded: 18,857 bytes in 1 files **************************************** I then determined that the downloaded file is not correct. It is not the file that tells me that I dont have a password. But some different incorrect file. The error is the same if I use the netscape 4 or 6 version of the cookies. This is the command that I was last using and it happend to be for the netscape 4 version. wget -i members2.txt -O output --load-cookies "C:\Program Files\Netscape\Users\morgan\cookies.txt" What is Set-Cookie? It sounds like something happening between wget and the remote server. Thanks. Brent Morgan Oceaneering Space Systems 16665 Space Center Blvd Houston TX 77058 (281) 228 5454 eFAX (419) 821-4826 [EMAIL PROTECTED] >>> Hrvoje Niksic <[EMAIL PROTECTED]> 01/14/02 07:37AM >>> "Brent Morgan" <[EMAIL PROTECTED]> writes: > Does anyone know how to handle password protected websites, for which > you have a password. (mapblast.com) > > usually with a webbrowser, you can access pages again and again. Can > it make use of IE or Netscape cookies? Yes. See the documentation of `--load-cookies' in Wget 1.8.1: `--load-cookies FILE' Load cookies from FILE before the first HTTP retrieval. FILE is a textual file in the format originally used by Netscape's `cookies.txt' file. You will typically use this option when mirroring sites that require that you be logged in to access some or all of their content. The login process typically works by the web server issuing an HTTP cookie upon receiving and verifying your credentials. The cookie is then resent by the browser when accessing that part of the site, and so proves your identity. Mirroring such a site requires Wget to send the same cookies your browser sends when communicating with the site. This is achieved by `--load-cookies'--simply point Wget to the location of the `cookies.txt' file, and it will send the same cookies your browser would send in the same situation. Different browsers keep textual cookie files in different locations: Netscape 4.x. The cookies are in `~/.netscape/cookies.txt'. Mozilla and Netscape 6.x. Mozilla's cookie file is also named `cookies.txt', located somewhere under `~/.mozilla', in the directory of your profile. The full path usually ends up looking somewhat like `~/.mozilla/default/SOME-WEIRD-STRING/cookies.txt'. Internet Explorer. You can produce a cookie file Wget can use by using the File menu, Import and Export, Export Cookies. This has been tested with Internet Explorer 5; it is not guaranteed to work with earlier versions. Other browsers. If you are using a different browser to create your cookies, `--load-cookies' will only work if you can locate or produce a cookie file in the Netscape format that Wget expects. If you cannot use `--load-cookies', there might still be an alternative. If your browser supports a "cookie manager", you can use it to view the cookies used when accessing the site you're mirroring. Write down the name and value of the cookie, and manually instruct Wget to send those cookies, bypassing the "official" cookie support: wget --cookies=off --header "Cookie: NAME=VALUE"
