Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I'm not familiar with those commands, but here is what they produce:

(Please excuse the formatting.)

lwp-request -m get -USsexd http://mail-scanning/cgi-bin/temp.cgi
skx@gold:~$ lwp-request -m get -USsexd http://mail-scanning/cgi-bin/te +mp.cgi LWP::UserAgent::new: () LWP::UserAgent::request: () LWP::UserAgent::send_request: GET http://mail-scanning/cgi-bin/temp.cg +i LWP::UserAgent::_need_proxy: Not proxied LWP::Protocol::http::request: () LWP::Protocol::collect: read 8 bytes LWP::Protocol::collect: read 387 bytes LWP::UserAgent::request: Simple response: OK GET http://mail-scanning/cgi-bin/temp.cgi User-Agent: lwp-request/5.810 GET http://mail-scanning/cgi-bin/temp.cgi --> 200 OK Connection: close Date: Thu, 14 Aug 2008 21:15:16 GMT Location: http://example.com/ Server: Apache/2.2.9 (Debian) PHP/5.2.6-2+b1 with Suhosin-Patch mod_ss +l/2.2.9 OpenSSL/0.9.8g mod_musicindex/1.2.2 mod_perl/2.0.4 Perl/v5.10 +.0 Content-Type: text/plain Client-Date: Thu, 14 Aug 2008 21:15:16 GMT Client-Peer: 192.168.1.10:80 Client-Response-Num: 1 Client-Transfer-Encoding: chunked

The second  lwp-request -m get -USsex http://mail-scanning/cgi-bin/temp.cgi

LWP::UserAgent::new: () LWP::UserAgent::request: () LWP::UserAgent::send_request: GET http://mail-scanning/cgi-bin/temp.cg +i LWP::UserAgent::_need_proxy: Not proxied LWP::Protocol::http::request: () LWP::Protocol::collect: read 8 bytes LWP::Protocol::collect: read 387 bytes LWP::UserAgent::request: Simple response: OK GET http://mail-scanning/cgi-bin/temp.cgi User-Agent: lwp-request/5.810 GET http://mail-scanning/cgi-bin/temp.cgi --> 200 OK Connection: close Date: Thu, 14 Aug 2008 21:16:29 GMT Location: http://example.com/ Server: Apache/2.2.9 (Debian) PHP/5.2.6-2+b1 with Suhosin-Patch mod_ss +l/2.2.9 OpenSSL/0.9.8g mod_musicindex/1.2.2 mod_perl/2.0.4 Perl/v5.10 +.0 Content-Type: text/plain Client-Date: Thu, 14 Aug 2008 21:16:29 GMT Client-Peer: 192.168.1.10:80 Client-Response-Num: 1 Client-Transfer-Encoding: chunked redirect<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>200 OK</title> </head><body> <h1>OK</h1> <p>The document has moved <a href="http://example.com/">here</a>.</p> <hr> <address>Apache/2.2.9 (Debian) PHP/5.2.6-2+b1 with Suhosin-Patch mod_s +sl/2.2.9 OpenSSL/0.9.8g mod_musicindex/1.2.2 mod_perl/2.0.4 Perl/v5.1 +0.0 Server at mail-scanning Port 80</address> </body></html>
Steve
--

In reply to Re^2: Failure to redirect when my CGI::Application powered site is used under mod_perl2 by skx
in thread Failure to redirect when my CGI::Application powered site is used under mod_perl2 by skx

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others goofing around in the Monastery: (9)
As of 2024-04-18 08:08 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found