Hi,
Did somebody else observe the following problem:
Environment: IIS on WinNT. Latest Tomcat with isapi. A jsp, which is invoked
by submitting a form with method=POST.
Problem: The jsp page is invoked, but none of the form parameters (i.e. a
field inside the form) is communicated to the jsp. The
request.getParameter("myField") returns null, despite that the field
definitely has data.
If I change the form from POST to GET, everything works.
If I substitute the jsp with a servlet, everything works with POST.
An interesting point is that if I had the mapping *.jsp -> Tomcat defined in
uriworkermap.properties, the parameter value is correctly sent to the jsp,
with POST. But if I define the mapping in the IIS application settings, the
request seems to be empty, with no parameters. The problem does NOT go away
if I define the mapping in both uriworkers and application settings.
However, it seems that I have to use application settings - if I dont, the
password-based authentication mechanism simply does not work.
Below is a summary of my observations:
Case 1.
Mapping in uriworkermap: Yes.
Mapping in IIS application: No.
POST. getParameter: returns correct data
getRemoteUser: null. IIS doesn't even asks for the password.
Case 2.
Mapping in uriworkermap: No.
Mapping in IIS application: Yes.
POST. getParameter: returns null
getRemoteUser: IIS asks for the password, and the method returns correct
value
Case 3.
Mapping in uriworkermap: Yes.
Mapping in IIS application: Yes.
POST. getParameter: returns correct value
getRemoteUser: null. IIS doesn't even asks for the password.
It seems that mapping in uriworkermap takes priority over the mappings
specified for the IIS application. But I may be wrong here.
Any help will be appreciated.
Regards
Michael
-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended
for the addressee(s) only. If you have received this message in error or
there are any problems please notify the originator immediately. The
unauthorized use, disclosure, copying or alteration of this message is
strictly forbidden. Baltimore Technologies plc will not be liable for direct,
special, indirect or consequential damages arising from alteration of the
contents of this message by a third party or as a result of any virus being
passed on.
In addition, certain Marketing collateral may be added from time to time to
promote Baltimore Technologies products, services, Global e-Security or
appearance at trade shows and conferences.
This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
