W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997

Re: Interoperability Test 10-23

From: Life is hard... and then you die. <Ronald.Tschalaer@psi.ch>
Date: Mon, 20 Oct 1997 14:42:50 +0200
Message-Id: <97102014424987@psiclb.psi.ch>
To: HTTP-WG%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4581

>  Some notes from the first day:
>     Origin Servers - it would be helpfull if the content available
>        from  your test server was in some way self-descriptive so
>        that, for example, testers can tell which pages should be
>        cachable, which should produce chunked output, and so forth.

Having run one of the clients in this test I'd like to second this
request. Ideally, if the folks who provide servers could even give a
rough idea beforehand of what's on their server, that would help me (and
I presume other clients) in preparing some tests. For example it would
be useful to know what request methods can be tested and on which URLs
(this includes the URLs for various forms).

Also, since I've noticed that a number of problems turn up in conjuction
with dynamic content (cgi scripts, SSI, etc). I would therefore like to
see more of this. Specifically, cgi's which produce a Content-length
header, cgi's which don't, cgi's which return 3xx responses, cgi's with
varying cache-control headers, etc would be useful. I know this means
extra work for all those putting up servers, but those of us with
clients have some work trying to put together, run and debug tests
against the servers (I'm not complaining, just pointing out).


Received on Monday, 20 October 1997 06:09:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC