Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

streamsniff 0.04 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News streamsniff 0.04 (Default branch)
# 1  
Old 05-12-2008
streamsniff 0.04 (Default branch)
Streamsniff is a small command line tool that sniffs network traffic for stream URLs. It detects RTSP, MMS, and icy protocols, and performs a backtrace on HTTP traffic to detect "playlist" URLs and Flash video files. This is useful when you want to reveal the stream you started with your browser and don't feel like digging through loads of HTML and Javascript.License: GNU General Public License (GPL)Changes:
This is a maintenance release.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

lwp::debug

LWP::Debug(3)						User Contributed Perl Documentation					     LWP::Debug(3)

NAME

       LWP::Debug - deprecated

DESCRIPTION

       LWP::Debug 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 happen to use the old interfaces continue to run.

       One useful feature that LWP::Debug provided (in an imprecise and troublesome way) was network traffic monitoring.  The following section
       provide some hints about recommened replacements.

   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 higly recommended for this.

       Another approach it 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::UserAgent

perl v5.18.2							    2012-01-13							     LWP::Debug(3)