Hi Mike,
as I have written earlier, I have the following problem with HtmlUnit.
If I have a form with more than one submit-button, HtmlUnit seems to
send all buttons and their values in the post request. Our web
application decides what to do after such a request, by checking, if a
certain button was send or not. So, if the cancel button is send, it
thinks, cancel was pressed, even if the ok button was send also.
I had the problem with HtmlUnit 1.1 pre5 and I have that problem still
with HtmlUnit 1.1 final with up to date commons httpclient
(commons-httpclient-2.0-alpha2).
Some weeks ago I have examined the whole problem a little bit closer and
send you an mail. Unfortunately I sent it to the wrong address it seems,
since it never reached the list.
However, I think HtmlUnit has a problem, if there are upper case
attributes in the input-element. In my example code a button like <input
type=SUBMIT .. > didn't work and behaved like described above, while
HtmlUnit accepted a button like <input type=submit ..> and behaved
correctly.
Would be nice if you could fix this, since its a nasty piece of work to
go through our application and change everything (even though upper case
html-code is not xhtml-conform).
Will there be a patch package available soon or do I have to work with
cvs builds? At least it would be cool, to have a package with the up to
date commons http client included. You would prevent people from running
into that HTTP/1.1 problem.
Kind regards from Germany,
Thomas Bartz
|
