"Robin B. Lake" <[EMAIL PROTECTED]> writes: > I am trying to get real-time stock quotes from my broker's Web site. > If I come in via an http:// request, I get 20-minute delayed data. > If I log in with my name and password via my browser, I get > real-time data. By monitoring the IP packets, it seems that I'm > being fed a cookie. > > Wget does a fantastic job on the http:// connection! But I can't > seem to get the https:// connection to work correctly. Do you > have any suggestions, please?
There are two different issues here: * Having Wget transmit a cookie to the server to inform the server of your identity; * Using https to retrieve the data. The two are not equivalent. The first problem can be solved like this: if you're using netscape, log in with it to the site. Then get the stock quotes like this: wget --load-cookies ~/.netscape/cookies.txt http://... That should tell Wget to load netscape's cookies and use them when talking to a server. If you're using Mozilla, it would look like this: wget --load-cookies ~/.mozilla/default/your-profile-name/cookies.txt http://... Let me know if that works. As for your second problem, to use https, you need to compile Wget with SSL support. To do that, you need the OpenSSL libraries and you need to specify `--with-ssl' to `configure'. If this succeeds, SSL downloads should work.
