Bug getting post args?

[Robert Lucier <ro...@yahoo.com>]

Hello,

I found a bug in Tomcat 4.0 final when trying to get POST parameters. I
have a form with method=post which is processed by a servlet which
worked fine with TC3.2.x. Now that servlet is not receiving the post
args at all with request.getParameter (but still receives the query
args just fine). It *does* work if I call request.getParameter() as the
very first method in the service() call.

Has anyone else seen this kind of thing? Any ideas on where to look for
a problem?

Regards,

Rob


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

RE: IIS isapi_redirector.dll bad experience

[Ylan Segal <yl...@digiworks.tv>]

Yeah.. maybee you are right.. It's just that I am used to linux as a server
environment, and have my tomcat/apache installation working very fast, but
my client has a windows server and there is no way to change that.

Ylan.

> -----Original Message-----
> From: Mikael Aronsson [mailto:mikael-aronsson@telia.com]
> Sent: Friday, October 12, 2001 8:06 PM
> To: tomcat-user@jakarta.apache.org
> Subject: Re: IIS isapi_redirector.dll bad experience
>
>
> Hi !
>
> I think most Windows users know about this already, most people do a
> uninstall/reinstall if everything doesn't work as expected now and then
> anyway ;o)
>
> I have even heard about users that complained about their
> WindowsME took so
> long to restart WHEN it crashed, they where not very upset about the fact
> that their WindowsME crashed now and then, they where used to that.....
>
> With that said, NT/2000 is much better of course and maybe a short note
> about this could be helpful even though I don't think this is a common
> problem, you just had a very bad day (or two).
>
> Mikael
>
> ----- Original Message -----
> From: "Ylan Segal" <yl...@digiworks.tv>
> To: <to...@jakarta.apache.org>
> Sent: Saturday, October 13, 2001 1:45 AM
> Subject: IIS isapi_redirector.dll bad experience
>
>
> > Hi,
> >
> > I had a very bad experience installing isapi_redirector.dll
> recently, and
> I
> > think maybee the documentation could be upgraded to save other people in
> the
> > same situation some time. Let me explain:
> >
> > My environment:
> > Windows 2000 workstation.
> > IIS 5
> > tomcat 3.2.3
> > Java SDK 1.3.1
> >
> > I started by following all the instructions provided in the
> documentation
> to
> > make tomcat cooparate with IIS (out of process). I am used to
> using tomcat
> > with apache, but it was my first time trying it in IIS.
> >
> > I followed the instructions to the dot, only to find that IIS
> was sending
> a
> > 403 error. Of course, my first action was to check the troubleshooting
> > portion of the docs and sure enough, my problem was listed.. the culprit
> was
> > named as Execute Access not being set in the "jakarta" virtual
> directory.
> I
> > fixed this but, to no avail.
> >
> > So I started doing some digging around and searched extensivley in the
> > archives for people who had the same problem and tried everything. After
> two
> > days, I found that the actual problem was not in the configuration, the
> dll
> > or anything like that, but IIS itself. Somehow the installation was
> > corrupted (with absolutley no indication that it was). The problems went
> > away when I unistalled IIS and resintalled again. After that the
> > instructions in the docs worked like a charm the first time
> around and it
> > was smooth sailing from then on. I had just spent two days on
> something I
> > could have finished in 30 minutes.
> >
> > So... my point, besides venting my frustration to people who understand
> what
> > it is like (my girlfriend is not that sympathetic), is that maybee we
> could
> > include a warning in the troubleshooting part of the docs that says
> > something like:
> > "If you are certain that all instructions where followed to the letter,
> and
> > still having no luck, please note that some users have fixed this by
> > re-installing IIS".
> >
> >
> > What do you guys think?
> >
> > Ylan Segal.
> >
> >
>
>

Re: IIS isapi_redirector.dll bad experience

[Mikael Aronsson <mi...@telia.com>]

Hi !

I think most Windows users know about this already, most people do a
uninstall/reinstall if everything doesn't work as expected now and then
anyway ;o)

I have even heard about users that complained about their WindowsME took so
long to restart WHEN it crashed, they where not very upset about the fact
that their WindowsME crashed now and then, they where used to that.....

With that said, NT/2000 is much better of course and maybe a short note
about this could be helpful even though I don't think this is a common
problem, you just had a very bad day (or two).

Mikael

----- Original Message -----
From: "Ylan Segal" <yl...@digiworks.tv>
To: <to...@jakarta.apache.org>
Sent: Saturday, October 13, 2001 1:45 AM
Subject: IIS isapi_redirector.dll bad experience


> Hi,
>
> I had a very bad experience installing isapi_redirector.dll recently, and
I
> think maybee the documentation could be upgraded to save other people in
the
> same situation some time. Let me explain:
>
> My environment:
> Windows 2000 workstation.
> IIS 5
> tomcat 3.2.3
> Java SDK 1.3.1
>
> I started by following all the instructions provided in the documentation
to
> make tomcat cooparate with IIS (out of process). I am used to using tomcat
> with apache, but it was my first time trying it in IIS.
>
> I followed the instructions to the dot, only to find that IIS was sending
a
> 403 error. Of course, my first action was to check the troubleshooting
> portion of the docs and sure enough, my problem was listed.. the culprit
was
> named as Execute Access not being set in the "jakarta" virtual directory.
I
> fixed this but, to no avail.
>
> So I started doing some digging around and searched extensivley in the
> archives for people who had the same problem and tried everything. After
two
> days, I found that the actual problem was not in the configuration, the
dll
> or anything like that, but IIS itself. Somehow the installation was
> corrupted (with absolutley no indication that it was). The problems went
> away when I unistalled IIS and resintalled again. After that the
> instructions in the docs worked like a charm the first time around and it
> was smooth sailing from then on. I had just spent two days on something I
> could have finished in 30 minutes.
>
> So... my point, besides venting my frustration to people who understand
what
> it is like (my girlfriend is not that sympathetic), is that maybee we
could
> include a warning in the troubleshooting part of the docs that says
> something like:
> "If you are certain that all instructions where followed to the letter,
and
> still having no luck, please note that some users have fixed this by
> re-installing IIS".
>
>
> What do you guys think?
>
> Ylan Segal.
>
>

IIS isapi_redirector.dll bad experience

[Ylan Segal <yl...@digiworks.tv>]

Hi,

I had a very bad experience installing isapi_redirector.dll recently, and I
think maybee the documentation could be upgraded to save other people in the
same situation some time. Let me explain:

My environment:
Windows 2000 workstation.
IIS 5
tomcat 3.2.3
Java SDK 1.3.1

I started by following all the instructions provided in the documentation to
make tomcat cooparate with IIS (out of process). I am used to using tomcat
with apache, but it was my first time trying it in IIS.

I followed the instructions to the dot, only to find that IIS was sending a
403 error. Of course, my first action was to check the troubleshooting
portion of the docs and sure enough, my problem was listed.. the culprit was
named as Execute Access not being set in the "jakarta" virtual directory. I
fixed this but, to no avail.

So I started doing some digging around and searched extensivley in the
archives for people who had the same problem and tried everything. After two
days, I found that the actual problem was not in the configuration, the dll
or anything like that, but IIS itself. Somehow the installation was
corrupted (with absolutley no indication that it was). The problems went
away when I unistalled IIS and resintalled again. After that the
instructions in the docs worked like a charm the first time around and it
was smooth sailing from then on. I had just spent two days on something I
could have finished in 30 minutes.

So... my point, besides venting my frustration to people who understand what
it is like (my girlfriend is not that sympathetic), is that maybee we could
include a warning in the troubleshooting part of the docs that says
something like:
"If you are certain that all instructions where followed to the letter, and
still having no luck, please note that some users have fixed this by
re-installing IIS".


What do you guys think?

Ylan Segal.