LWP::Debug(3)

okay so bestie, welcome to the LWP::Debug(3) page from the User Contributed Perl Documentation — and the whole vibe is deprecated, no cap. 💅

💖 NAME 💖

• LWP::Debug — deprecated. that's the whole name. 😭

🌸 DESCRIPTION 🌸

This module has been deprecated. Please see LWP::ConsoleLogger for your debugging needs. fr fr.

LWP::Debug is used to provide tracing facilities, but these are not used by LWP any more. The code in this module is kept around (undocumented) so that 3rd party code that happens to use the old interfaces continue to run. iykyk.

One useful feature that LWP::Debug provided — in an imprecise and troublesome way — was network traffic monitoring. The following section serves up some hints about recommended replacements. lowkey important. ✨

🦋 Network traffic monitoring 🦋

The best way to monitor the network traffic that LWP generates is to use an external TCP monitoring program. The WireShark program (http://www.wireshark.org/) is highly recommended for this. it's giving packet-queen energy. 🎀

Another move is to use a debugging HTTP proxy server and make LWP direct all its traffic via this one. Call $ua->proxy to set it up and then just use LWP as before. 🫶

For less precise monitoring needs just setting up a few simple handlers might do. The following example sets up handlers to dump the request and response objects that pass through LWP:

use LWP::UserAgent;
$ua = LWP::UserAgent->new;
$ua->default_header('Accept-Encoding' => scalar HTTP::Message::decodable());

$ua->add_handler("request_send",  sub { shift->dump; return });
$ua->add_handler("response_done", sub { shift->dump; return });

$ua->get("http://www.example.com");

✨ SEE ALSO ✨

• LWP::ConsoleLogger — bestie, this is the one for your debugging needs. 💖
• LWP::ConsoleLogger::Everywhere — the everywhere edition. 🌈
• LWP::UserAgent — the LWP user agent itself. 👑

---

k bye bestie, this page is from perl v5.42.0, dated 2026-05-18. stay debuggy. 💜