Hi Greg,
as you know Digest Authentication is a "little" complex, so I keep
inside the source some TODO, mainly to remember that there are some
cases that are not tested at the moment ... but many of them was
handled in the same way (without TODOs) also in other libraries.

We can remove them, and the rest of commented code inside ... but
before doing this I'd like to wait some time, so if someone try it can
have more info. What do you think ?

Some things to note:
- under test I've added two JUnit Test classes:
WebQueryTestClientBasic and WebQueryTestClientDigest , but nothe that
these are "Integration Tests" so they need a working www server on
localhost (and setup in the right way), so if we'll enable automatic
test running at any Compile / Deploy via Ant, these should be excluded
... they could be moved inside another test directory, or excluded in
another way, but i think it's important to keep them in some place
here, under the test area
- to test this you can follow my instructions in the README, to setup
folders and permissions on an Apache 2.0.x or 2.2.x running on
localhost
- I'll make some test under Tomcat as soon as possible (this is my
first and maybe the only TODO) to finish this part ...
- for the README to migrate to package html file, have you got some
idea / hint / sample for me ? Thanks.


Ah, one quick note:
I've seen today that the latest Apache 2.2.x under Vista doesn't work
very well (in default htdocs doesn't take right permissions, the
service starts but in a wrong way, etc) ... but also here after many
manual settings, all works on my environment.
So, the real, important point to finish this part is:
this is a complex feature, and needs more testing, or better, not only
from me ...

In any case, be free to modify code if you want.
FindBugs has no warning on it :-) ...


Comments ?

Bye

Reply via email to