« Setting HTTP Timeouts for a SOAP client | Main | Announcing the SOAP::Lite Logo Contest »


Luigino Masarati

In the SOAP::Trace documentation, the 'debug' signal is documented as "Client or Server", but it is a client only signal.
If you want to trace request and response as string also when acting as a soap server, you must add 2 lines in /SOAP/Transport/HTTP.pm file:

sub handle {
my $self = shift->new;

SOAP::Trace::debug($self->request->as_string); # log incoming request

sub make_response {
SOAP::Trace::debug($self->response->as_string); # log outgoing response

What do you think about adding them in the next release?


praveen castelino


We are using http->request(url) to retrieve PDF file from the Server. This works fine if the server is up and running.
In case, if the server is down (i.e. if the main server is down then there is a leveler( intermediate ) circuit which redirects into a back-up server ) then this function fails and the error code is 302. Please let us know, if there is any alternate method.......

Existing Code:-
$http = new HTTP::Lite;
$req = $http->request ($reqStr)

I need your help as Perl scripting and Web applications concepts are completely new to me.
Also, please let me know, if there are any other modules (like HTTP::Lite) which I can use.


star trek gold

but for now, one still needs to do a little more work. The following code sample shows how one can extend SOAP::Transport::HTTP:CGI to intercept both the HTTP request and the HTTP response prior to it being processed and/or returned respectively.

The comments to this entry are closed.