in reply to Re^3: Is anyone at perlmonks aware that... (browser vs lwp-request)
in thread Is anyone at perlmonks aware that...

I think the best approach is to leave DNS completely out of the picture.

Currently, http://216.92.2.139/~perl2 http://216.92.34.251/index.pl (which is also accessible via sending the appropriate Host: header and accessing the IP address directly) serves a blank page for me, most likely because the cached frontpage has been generated empty.

  • Comment on Re^4: Is anyone at perlmonks aware that... (browser vs lwp-request)
  • Download Code

Replies are listed 'Best First'.
Re^5: Is anyone at perlmonks aware that... (browser vs lwp-request)
by BrowserUk (Patriarch) on Jun 02, 2011 at 19:43 UTC

    My ignorance of web servers means I don't understand most of that.

    I can say that the link also renders a blank page which view source displays empty.

    But then, if I give that url to lwp-request it also comes up empty, so whether than is useful information I have no idea.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

      I've (again) restarted the Apache server. mod_perl currently throws errors for SQL statements that otherwise run fine, so maybe some memory corruption happens for long-running processes...

      DBD::mysql::st execute failed: You have an error in your SQL syntax; c +heck the manual that corresponds to your MySQL server version for the + right syntax to use near ' NOW() )

      for

      my $in= $DB->getDatabaseHandle->prepare( 'REPLACE INTO iplog( user_id, ip_id, tstamp )' . ' VALUES( ?, ?, NOW() )' ); $in->execute( getId($USER), $ip );

      Update: (and looking at the mysql access log, it is even right in its error message (one IP address redacted, the other, blank space is as-is)):

      1566594 Query REPLACE INTO iplog( user_id, ip_id, + tstamp ) VALUES( '5348', 1234567890, NOW() ) 1566350 Query REPLACE INTO iplog( user_id, ip_id, + tstamp ) VALUES( '806480', , NOW() )

      As to who/what circumstances allow DBD::mysql (3.0008) to create this invalid SQL for the placeholder-guarded statement is quite unclear to me.