Webserver quality checking programm

  • Thread starter Thread starter Michel Firholz
  • Start date Start date
M

Michel Firholz

Hi Group,
could anyone recommend a good freeware webserver quality checking program?

Thanks.
Michel
 
could anyone recommend a good freeware webserver quality checking program?
Click to expand...

Maybe - it depends on the exact definition of "webserver quality".
Apache's a quality web server. Do you mean competent HTML code?
Something pleasing to the eye? The phrase can mean all sorts of
things, objective and subjective.
 
Al Klein said:
Maybe - it depends on the exact definition of "webserver quality".
Apache's a quality web server.
Click to expand...

You are right, let me define it clearly:
I meant a routine, which is periodically monitoring if a web server is
upright and accessible.
Additionally it should monitor the response time to deliver a given page.
Last but not least, it should be able to test if a SSL coded page is
accessible.
Do you mean competent HTML code?
Something pleasing to the eye? The phrase can mean all sorts of
things, objective and subjective.
Click to expand...

not really: neither are HTML content is, nor are design considerations or
even broken links to be considered as being "web_server_ quality", but much
more beeing "web_site_ quality".
 
You are right, let me define it clearly:
I meant a routine, which is periodically monitoring if a web server is
upright and accessible.
Additionally it should monitor the response time to deliver a given page.
Last but not least, it should be able to test if a SSL coded page is
accessible.
Click to expand...

A trivial little web control and 2 timers. I could probably do it in
VB in an hour if I took a look at exactly what SSL entailed - I've
never coded for it. But reading your above paragraph roughed out most
of the non-SSL program for me.

Then again, look into tcl - it should be pretty trivial there too. Or
a little Perl script running on your computer.

"Periodically" means kick off a timer every - what? 5 minutes? Wait,
oh, 60 seconds. If no response, the sites not there, otherwise log
the time it took for the return.

Now do the SSL stuff, what ever that will be.
 
Al Klein skrev:
A trivial little web control and 2 timers. I could probably do it in
VB in an hour if I took a look at exactly what SSL entailed - I've
never coded for it. But reading your above paragraph roughed out most
of the non-SSL program for me.
Click to expand...

No need to reinvent the wheel. A simple script can call a simple
SSL-enabled browser, such as Lynx, and use it to dump a given URL. After
that it's all a matter of timing the response and verifying the contents
of the dump.
 
Al Klein skrev:
Click to expand...
No need to reinvent the wheel. A simple script can call a simple
SSL-enabled browser, such as Lynx, and use it to dump a given URL. After
that it's all a matter of timing the response and verifying the contents
of the dump.
Click to expand...

I haven't done any scripting in years, but your trivial is more
trivial than mine. :)
 
Al Klein said:
A trivial little web control and 2 timers. I could probably do it in
VB in an hour if I took a look at exactly what SSL entailed - I've
never coded for it. But reading your above paragraph roughed out most
of the non-SSL program for me.

Then again, look into tcl - it should be pretty trivial there too. Or
a little Perl script running on your computer.

"Periodically" means kick off a timer every - what? 5 minutes? Wait,
oh, 60 seconds. If no response, the sites not there, otherwise log
the time it took for the return.

Now do the SSL stuff, what ever that will be.
Click to expand...

I wonder. If it were tha trivial, a plugin for Firefox would have existed.
 
I wonder. If it were tha trivial, a plugin for Firefox would have existed.
Click to expand...

The original request was a trivial one, so why should the solution be
less trivial? (I mean "trivial" in a systems analysis way, I'm not
denigrating the original request.)
 
Back
Top