>We have a protocol problem. Section 8.2.4 says that we MUST return
>an "error status" if we don't return a 100. That shouldn't say what
>kind of other status the server might return, since some requests can
>be completed successfully without reading the body (e.g., the OPTIONS
>body can be discarded). 302 responses is another case where the
>server does not want to return 100 even though it is not an error.
I think this can be fixed by replacing "error status" with
"final status code" throughout section 8.2.4.
....Roy