[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #9 from Mark Thomas --- Another idea. Add a new option cgiMethods which is a comma separated list of methods to pass to the CGI script (or * for all methods). Requests using one of those methods are always passed to the script.

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #8 from Konstantin Kolinko --- (In reply to Mark Thomas from comment #7) > My current thinking is to add a single new option, enableAllHttpMethods. If > this is enabled, every request regardless of method

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #7 from Mark Thomas --- 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

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #6 from Mark Thomas --- Good point. Fixing that starts heading in the direction of the original patch again. More thought required. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #5 from jm009 --- > Unless there are objections then I propose the following: > - allow any HTTP method and let the CGI script decide how to handle it Sounds good. > - except HEAD, TRACE and OPTIONS which

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #4 from Mark Thomas --- Currently, the CGI servlet only handles a request body if the method is POST and the Content-Length header is set. Unless there are objections then I propose the following: - allow any

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #3 from jm009 --- (In reply to jm009 from comment #2) > How to determine in this case, if request body data (a.k.a. "POST data") > should be forwarded to the servlet? If I get it right, this reverse proxy

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #2 from jm009 --- (In reply to Christopher Schultz from comment #1) > I don't like this patch (-1) for a number of reasons. > > 1. It uses many regular expressions during each request: poor performance

[Bug 61692] CGIServlet should handle additional HTTP methods, for example MKCALENDAR, MKCOL, PROPFIND, PROPPATCH

https://bz.apache.org/bugzilla/show_bug.cgi?id=61692 --- Comment #1 from Christopher Schultz --- I don't like this patch (-1) for a number of reasons. 1. It uses many regular expressions during each request: poor performance 2. It requires configuration for what