enough of them to trigger the dumb robot alert.
>That means they should
>take along time to return, right? None of them took but a few seconds.
No. You're making more assumptions. Ever heard of a background process?
The CPU intensive stuff is performed in the background (on another
machine in this case). The request returns immediately.
>> Almost all the URLs you listed fire off CGI.
>
>Do CGI's return "last modified dates"? Not under Netscape's servers, maybe
>under someone else's?
What does this have to do with anything? Are you clutching at straws
to justify dumb assumptions. xxx.lanl.gov has scripts that send back
last modified dates, so that gives you a good enough reason to launch
a robotic attack in defiance of the robot.txt file on that site?.
>
>"Almost all" of the URLs were these. The second number is the LMD (in system
>time).
>
>http://xxx.lanl.gov/abs/hep-ph/9606247 834007794 text/html
>http://xxx.lanl.gov/abs/hep-th/9604095 829740893 text/html
>http://xxx.lanl.gov/abs/hep-ph/9606238 833929321 text/html
>http://xxx.lanl.gov/abs/hep-ph/9605439 833461350 text/html
So what? script output can have a last modified time if the content
can be described that way.
The longer you prolong this thread, the more you expose your ignorance..
which isn't such a bad thing because I'm sure there are plenty of
wannabe robot writers listening to this who can learn from your
mistakes.
Can you see you've made dumb assumptions and that your actions
could easily cause damage to a server or a denial of service?
rob