[ 
https://issues.apache.org/jira/browse/GERONIMO-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489219
 ] 

Paul McMahan commented on GERONIMO-2841:
----------------------------------------

I am past the error shown above now and can run the testcase.    After looking 
further into this I don't have high hopes of a simple solution for this.   
According to tomcat's svn logs the configuration option was purposely removed 
in order to guarantee spec compliant behavior.  i.e. section 9.10 of the 2.4 
servlet spec says when an http client makes a request using the context path 
without the trailing slash that the server should redirect the client to make 
the same request using a trailing slash.    */foo* gets redirected to */foo/*

The options that I can think of (in order of preference) are:
# try to override or somehow avoid the behavior in tomcat for contexts 
associated with web services.  I'm just about out of ideas for this though.
# rearchitect the web service support in the Tomcat assembly to create a 
servlet for each web service instead of a context.  this would require 
significant effort and be inconsistent with the jetty assembly.
# leave the current design in place with its limitations and expect the WS 
client to use POST instead of GET when its original POST is redirected
# ask Tomcat to provide a configuration option to reenable the non spec 
compliant behavior

> Valve reports request method as GET even though POST request was made
> ---------------------------------------------------------------------
>
>                 Key: GERONIMO-2841
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2841
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat
>            Reporter: Jarek Gawor
>         Assigned To: Paul McMahan
>
> The Request of EJBWebServiceValve in Tomcat return the request method as GET 
> even though POST request was sent. In similar class in Jetty the request 
> method is reported correctly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to