-
1. Re: Jetty fails to run POST
gregwilkins Sep 9, 2002 8:28 PM (in response to jackpark)I've had several reports like this - and the results have always been that a redirection is taking place on the POSTs and the client (IE) is turning the POST into a GET.
The redirection that Jetty does, that I don't think
tomcat does is to redirect /context to /context/
This is due to lack of clarity in the servlet spec and
the fact that a null or empty servletpath is not legal
within a context.
Anyway, I suggest that you look for such redirections
and change the target of the forms to include the trailing
slash. -
2. Re: Jetty fails to run POST
jackpark Sep 9, 2002 11:12 PM (in response to jackpark)Thank you, Greg.
Firstly, I'm using Mozilla, not IE.
Then, the nature of the response from the browser is based on the following code:
<input.....>
<input...>
Where one input is a save button, one is a text area, and the rest are hidden values.
The only result of that that I get to see is after the redirection and then, it's all gone.
The question is: where would I put the trailing slash? -
3. Re: Jetty fails to run POST
tbfmicke Sep 10, 2002 4:16 PM (in response to jackpark)I think the trailing slash is after wiki, so
try to change /wiki to /wiki/
Regards -
4. Re: Jetty fails to run POST
jackpark Sep 18, 2002 10:06 PM (in response to jackpark)I am most pleased to report that the suggestion seems to have corrected the problem. Still more testing to do, but it does look like that seems to have done the trick.
Many thanks.