Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TorgoX (1933)

TorgoX
  sburkeNO@SPAMcpan.org
http://search.cpan.org/~sburke/
"Il est beau comme la retractilité des serres des oiseaux rapaces [...] et surtout, comme la rencontre fortuite sur une table de dissection d'une machine à coudre et d'un parapluie !" -- Lautréamont
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

TEH INTERWEB 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I needed to webify some information not worthy of an Apache install, and so did a brief search through CPAN for an HTTP server module. To my surprise, I couldn't find one, so I pored through RFC 2616 and began writing my own. (The first thing I implemented was TRACE, which does exactly what you did.)

    Of course, while trying to clarify some vague points of 505 handling, Buggs was kind enough to point out HTTP::Daemon, which is part of libwww. (I had just browsed through HTTP::.) Oops. Well, saved me a

  • I use Interarchy on my Mac, which has the ability to show exactly what the contents of my requests are. So when I am debugging, I just view the headers in Interarchy. It used to be a separate package called OTSessionWatcher. Of course, you are unfortunate enough to not use Macs anymore. :)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.