This file documents some thoughts on a spec test framework.
-----------------------------------------------------------

It's really so that Paperclips developers can add requirements for
testing the code. At some later stage we can build these requirements
into a proper testing tool.

Updating this document
----------------------

Feel free to update this document with whatever conformance tests you
want. Make sure you provide the following information:

  a one line description of the test

  a more detailed description of the test

  a reference to the API or the HTTP spec (or some other spec)

  your name

If you don't do these things I am liable to back out your changes.


Nic Ferrier 
Feb 2001




HTTP Request spec conformance
------------------------

Test that a request aggregates parameters correctly with POST.
Any parameters specified in the query string have priority over
parameters specified in the POST. Where there is a clash Paperclips
should provide both values but the topmost value should be the value
from the query string.
API2.3-4.1
Added by: Nic

Test that POST parameters are passed at the correct time only.
A request must meet several criteria before POST data is actually
parsed: the request must be an HTTP or HTTPS request, the method must
be POST (duh!) and the content-type MUST be
application/x-www-form-urlencoded.
API2.3-4.1
Added by: Nic

Test that Paperclips can handle URIs of large lengths.
Paperclips ought to be able to handle URI lengths of up to 64K chars.
It would be usefull if it could do larger amounts.
HTTP/1.1
Added by: Nic


HTTP Response spec conformance
-------------------------



Session behaviour conformance
-----------------------------
