https://bz.apache.org/bugzilla/show_bug.cgi?id=61692
--- Comment #7 from Mark Thomas <ma...@apache.org> --- I've been thinking about this some more and experimenting with different ideas. Trying to reconcile the combination of maximising backwards compatibility, supporting any HTTP method and having the correct response for OPTIONS is not easy. Something has to give. My current thinking is to add a single new option, enableAllHttpMethods. If this is enabled, every request regardless of method will be passed to the CGI script and it will be expected to respond appropriately. This maximises backwards compatibility while enabling scripts to be deployed that support any methods. The downside is that if you enable this option the script has to handle OPTIONS, TRACE and any unrecognised methods. That seems a reasonable compromise to me. For the request body, I plan to go with the option of passing the request body for any method if Content-Length or Transfer-Encoding is set. This approach has the advantage that it can be applied to all supported Tomcat versions. I'll leave this a few days for folks to comment and if the consensus is favourable, I'll implement this approach for the next round of releases. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
