Problem with HttpUnit

Dear HttpUnit Team,

I do have a problem concerning cookie handling when using HttpUnit 1.7.
I try to monitor an application with login page that makes an redirect. 

Here is an short extract of the communication
***Request
GET https://a.b.c:456/login
***Response
HTTP 302 Found
SET-COOKIE=SECID=xyz; Domain=.a.b.c; path=/; Secure
LOCATION=/cookie-check

The cookie is rejected with reason 3 indicating that the domain 
attribute is not a suffix of the source domain issuing the cookie.
I suggest it is because of the leading dot in the domain attribute, 
also the order of the domain, path and secure attribute seems to be 
important.

My problem is that the communication works with IE(6.0 SP2) and 
FireFox(3.0.8) but not with HttpUnit. 
Even setting CookieProperties.setDomainMatchingStrict(false) doesn't 
bring a change.

So I do have the following questions:
Is there any chance to make WebClient behave as IE or FireFox?
If not, what is the reason why HttpUnit behaves that strict?
 
Mit freundlichen Grüssen / with kind regards
Andreas Ewertz


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com