httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacek Prucia <>
Subject Re: [PATCH] flood & verify_200
Date Tue, 02 Jul 2002 15:27:00 GMT
On Mon, 1 Jul 2002 10:44:44 -0700
Aaron Bannert <> wrote:

> I agree that working toward a beta might be a good plan. Right now
> I think the main obstacle to simple usability is the interface. For
> obvious reasons we haven't tried to make a polished interface, and
> IMHO that tends to impose unnecessary skill requirements on potential
> users. Ideally someone will come along and write a nice gui frontend
> that spits out XML directly in to flood.

Yeah, gtk frontend would be nice -- especially when creating complex
POST payloads...

> On the technical side, some of the things that remain to be done are:
>  - better modularity of the optional routines (possibly a runtime
>    dynamic linking feature if warranted)


>  - a way to run multiple verification tasks on the same response
>    (we have been looking to incorporate something similiar to httpd
>    2.0's
>     filters to accomplish this, but that is a lot of work and possibly
>     a redesign for this more general case)

Sure -- I've been thinking about more verify_resp functions. In
particular: verify_custom_header(), where we could verify response by
custom HTTP header, like -- X-Flood: OrderPlaced; $orderid=123 -- with
no need to regexp whole HTML body and verify_body() which could test if
responseteamplate has matched successfuly (even for general cases like
PHP warnings/errors and JSP backtraces). Without that filter-like
facility each of those functions probably schould include logic from
verify_status_code or verify_200.

>  - more optional routines (better verification routines, etc...)
>  - other features: 
>    - basic authentiation
>    - etc...

Ok. You just got yoursef a voulnteer :)

Jacek Prucia S.A.

View raw message