|
If you were logged in you would be able to see more operations.
|
|
|
|
When an unsupported HTTP method is called upon, the DispatcherServlet should raise an SC_METHOD_NOT_ALLOWED (405). Currently it throws an HttpRequestMethodNotSupportException instead. I couldn't find code that converts this exception to a 405 and the last time I found this was a while ago, so it could have been solved in the meantime... If so, please ignore ;-).
|
|
Description
|
When an unsupported HTTP method is called upon, the DispatcherServlet should raise an SC_METHOD_NOT_ALLOWED (405). Currently it throws an HttpRequestMethodNotSupportException instead. I couldn't find code that converts this exception to a 405 and the last time I found this was a while ago, so it could have been solved in the meantime... If so, please ignore ;-). |
Show » |
|
Improvement
Resolved
Major
DispatcherServlet should throw 405 when detecting an unsupported operation
In my case, I'm setting up a HessianServiceExporter. When I request the service via HTTP GET, the server I'm using (Tomcat) returns a 500 error condition. The HTTP spec gives status code 405 specifically to address this scenario.
I have no clue as to where it's appropriate to trap the HttpRequestMethodNotSupportException and cause it to set the appropriate 405 status headers. It seems that DispatcherServlet and the remoting related servlets have a different hierarchy and not common concrete class between them to handle HTTP responses. So, the fix here would likely involve needing a change multiple classes, probably including FrameworkServlet and HttpRequestHandlerServlet.