-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 6/9/2011 2:20 PM, André Warnier wrote:
> As I read the API for the ServletRequestListener, I understand that this
> thing is called very early in the cycle. The spirit seems to be :
> provide a way to warn as soon as possible that a servlet
Chris,
On 06/09/2011 06:13 PM, Christopher Schultz wrote:
First, log a bug in bugzilla. Then, get a copy of the source code
through svn. Edit the code, build it and test it (TC7 is much easier to
build than earlier versions).
Use "svn diff" to generate a patch file and attach that to the bug on
André,
sorry for my late response.
On 06/09/2011 08:20 PM, André Warnier wrote:
As I read the API for the ServletRequestListener, I understand that this
thing is called very early in the cycle. The spirit seems to be :
provide a way to warn as soon as possible that a servlet request has
come i
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon,
On 6/8/2011 1:47 PM, Simon Olofsson wrote:
I have a ServletRequestListener that tries too access a Request Parameter:
sre.getServletRequest().getParameter("x");
When I send a POST-Request with the "Expect: 100-co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon,
On 6/8/2011 1:47 PM, Simon Olofsson wrote:
> I have a ServletRequestListener that tries too access a Request Parameter:
> sre.getServletRequest().getParameter("x");
>
> When I send a POST-Request with the "Expect: 100-continue" HTTP Header
>
Hi,
I have a ServletRequestListener that tries too access a Request Parameter:
sre.getServletRequest().getParameter("x");
When I send a POST-Request with the "Expect: 100-continue" HTTP Header
it hangs waiting for the Request Body which isn't send because Tomcat
didn't send a 100-continue Res
