I figured this out, and it definitely had nothing to do with Wicket.
For anyone who cares:
It has to do with IE behavior relating to our NTML authentication filter
(JCIFS).
Essentially, once IE is forced to negotiate for a page (the first time it
hits the site), it assumes that all subsequent r
strange indeed. what is your wicket filter/servlet mapping? what does the
generated form markup look like?
-igor
On 2/1/07, dukejansen <[EMAIL PROTECTED]> wrote:
I'm facing a very strange issue which may be Wicket-related or may not.
It seems that for any form posts in our application, whet
I'm facing a very strange issue which may be Wicket-related or may not.
It seems that for any form posts in our application, whether Ajax or
otherwise, when the request arrives at the server there is no form data
included. The request.postData member is null.
This happens only in IE. Form posts
