Calling LWP in a template

Hi,

I'm having a problem with some perl code in a template that's driving me insane! Please Help!

Initially, it all worked fine on an older version of Teamsite but the same template does not work on a newer version...

My template contains code that performs a http post to an external server using the LWP libraries like this (for this example I've replaced the actual URL with a GET to 127.0.0.1 which still fails):


$ua = LWP::UserAgent -> new();
$request = HTTP::Request->new('GET', 'http://127.0.0.1/');
$response = $ua ->request($request);

This used to work fine but on my new server fails with:

Can't connect to 127.0.0.1:80 (Cannot determine protocol)

I've tested LWP by calling lwp-request with a system call:

This also fails with error 500.

However, if I login to the teamsite server as the same user I use to access Teamsite and
manually run this from the console:

> lwp-request -m GET -eUS http://127.0.0.1/

I get a response fine.

Also, if I use LWP to get a local file from within a template it works fine.

What's different about the perl environment between being called from the console and called from a template that would break networking?

Find more posts tagged with

Comments

Brendan

To further test, I tried to open a socket back to localhost like this:

use IO: Smiley Frustrated

ocket;

$server = '127.0.0.1';
$port = 80;

$socket = IO: Smiley Frustrated

ocket::INET->new(
Proto => 'tcp',
PeerAddr => $server,
PeerPort => $port,
Timeout => 10,
);
unless($socket) {
iwpt_output("Could not connect to $server:$port");
}

This connection also failed.

Migrateduser

This problem does not look to be TS specific (LWP is just a CPAN perl module after all). Please see the following thread I found on google:

http://archive.develooper.com/libwww@perl.org/msg03220.html

Please pay particular attention to the little bit of test code in the message as it may shed some light on the problem (I tested the code in question and it worked just fine.

What happens if you move your lwp code to just a perl script that is run through iwperl?

Migrateduser

Looks like we crossed streams. Please look at my earlier message and see what the results are from the test code from the url I posted may be.

Brendan

If I run:
lwp-request -m GET -eUS http://127.0.0.1/
from the command line, I get a response fine.
lwp-request is just a perl script that comes with the LWP distribution. This seems to suggest that LWP is installed and works ok.

if I call the same command via <iw_system> it fails.

I found another thread that may be related though...
check "inline callout and network access" from the forums -> Templating page.

Migrateduser

Well, the problem described in the other thread looks to be Windows specific. Are you also running on windows (I am guessing that this is the case currently from the comments made so far)? If so then what is stated in the other thread could very well be the same problem. I am uncertain of how to get around this however. There might be some sort of permission setting that can be set in windows to allow the script network resources, but I imagine that Microsoft put that protection in windows for a reason.

Migrateduser

What about:

print "getprotobyname: " . (getprotobyname('tcp'))[2] . "\n";

nyan

Did u got this solved? I like to have the solution if u already have. Thx!