07-22-2013
You could possibly try to save the cookies or session ids from an initial authenticated session. Experiment by using wget and look at --save-session-cookies and --keep-session-cookies (also --user, and --password) to get the initial value)
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
my host run on a Free bsd server and i have a cgi script that requires LWP module, but i my host say that that module is installed, so i would like to know if the is a command because i have telnet access to know if the module or which modules are installed on my account (itīs that the script donīt... (4 Replies)
Discussion started by: Beto
4 Replies
2. Shell Programming and Scripting
currently it has the following:
bdumpN=`ll /home/apps/oracle/admin/DBprod/bdump/DBprod_j* | grep "$Cdate" | wc -l`
If I pass the DBname, I would not have to hardcode it in the script...
I can capture the database name by adding the following:
DBname=$1
The problem is, I have been unable... (2 Replies)
Discussion started by: mr_manny
2 Replies
3. Solaris
Hi all
i want to do FTP via running a shell script and i want to hard code username and password for that particular server..
by writing it in a file can u help me in this regard..
Thank u
Naree (2 Replies)
Discussion started by: naree
2 Replies
4. UNIX for Dummies Questions & Answers
Hi
Can any one help me out ?
I am trying to send an autogenerated mail with an attachment to bulk of users using 'MAILX' and 'UNENCODE' . I have used it as follows
X " ( cat /sastemp/body.txt; uuencode Test.xls.gz Test.xls.gz ) | mailx -s 'Testing' ' abcd@yahoo.com , efgh@gmail.com ' "
... (9 Replies)
Discussion started by: manas6
9 Replies
5. Programming
This might be a silly question, but I thought I'd ask anyway. If I'm writing in C, isn't it more efficient to, for instance, use constant character variable set to 'A' instead of hard-coding a character 'A'? Since it's only a single character instead of a string, it might not matter much. (10 Replies)
Discussion started by: cleopard
10 Replies
6. Shell Programming and Scripting
Can some one tell me how to post the username and password using perl LWP. An example is sufficient.. (0 Replies)
Discussion started by: Anjan1
0 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I'm having a problem when I run the following code for example
perl -e 'use LWP::Simple; getprint "http://google.com"'
Can't locate LWP/Simple.pm in @INC (@INC contains: /System/Library/Perl/5.8.6/darwin-thread-multi-2level /System/Library/Perl/5.8.6... (7 Replies)
Discussion started by: pawannoel
7 Replies
8. Shell Programming and Scripting
Hi;
Can i have ne sample examples of of using " lwp-request" in shell script.
Is it necessary to have perl installed already in linux box for using this;
Thnks; (2 Replies)
Discussion started by: ajaypadvi
2 Replies
9. Hardware
Hi everyone
(see attachments)
I bought an HP Elitebook 8460p on eBay and it came with a password-locked Hitachi hard drive which I was told is the original hard drive. I don't know the password for the drive and running the diagnostics tools I see the hard drive is healthy. I tried booting... (9 Replies)
Discussion started by: milhan
9 Replies
LEARN ABOUT DEBIAN
coro::lwp
LWP(3pm) User Contributed Perl Documentation LWP(3pm)
NAME
Coro::LWP - make LWP non-blocking - as much as possible
SYNOPSIS
use Coro::LWP; # afterwards LWP should not block
ALTERNATIVES
Over the years, a number of less-invasive alternatives have popped up, which you might find more acceptable than this rather invasive and
fragile module. All of them only support HTTP (and sometimes HTTPS).
AnyEvent::HTTP
Works fine without Coro. Requires using a very different API than LWP. Probably the best choice iff you can do with a completely
different event-based API.
LWP::Protocol::AnyEvent::http
Makes LWP use AnyEvent::HTTP. Does not make LWP event-based, but allows Coro threads to schedule unimpeded through its AnyEvent
integration.
Let's you use the LWP API normally.
LWP::Protocol::Coro::http
Basically the same as above, distinction unclear. :)
AnyEvent::HTTP::LWP::UserAgent
A different user agent implementation, not completely transparent to users, requires Coro.
DESCRIPTION
This module is an AnyEvent user, you need to make sure that you use and run a supported event loop.
This module tries to make LWP non-blocking with respect to other coroutines as much as possible, and with whatever means it takes.
LWP really tries very hard to be blocking (and relies on a lot of undocumented functionality in IO::Socket), so this module had to be very
invasive and must be loaded very early to take the proper effect.
Note that the module AnyEvent::HTTP might offer an alternative to the full LWP that is designed to be non-blocking.
Here is what it currently does (future versions of LWP might require different tricks):
It loads Coro::Select, overwriting the perl "select" builtin globally.
This is necessary because LWP calls select quite often for timeouts and who-knows-what.
Impact: everybody else uses this (slower) version of select, too. It should be quite compatible to perls builtin select, though.
It overwrites Socket::inet_aton with Coro::Util::inet_aton.
This is necessary because LWP might (and does) try to resolve hostnames this way.
Impact: some code might not expect coroutine semantics, for example, when you fork you might prefer the blocking variant because other
coroutines shouldn't actually run.
It replaces the base class of Net::HTTP, Net::FTP, Net::NNTP.
This is necessary because LWP does not always use select to see whether a filehandle can be read/written without blocking, so the base
class "IO::Socket::INET" needs to be replaced by "Coro::Socket".
Impact: Coro::Socket is not at all compatible to IO::Socket::INET. While it duplicates some undocumented functionality required by LWP,
it does not have all the methods of IO::Socket::INET and might act quite differently in practise. Also, protocols other than the above
mentioned will still block, at least some of the time.
All this likely makes other libraries than just LWP not block, but thats just a side effect you cannot rely on.
Increases parallelism is not supported by all libraries, some might cache data globally.
AUTHOR
Marc Lehmann <schmorp@schmorp.de>
http://home.schmorp.de/
perl v5.14.2 2012-04-13 LWP(3pm)