enapps-enorman commented on pull request #6: URL: https://github.com/apache/sling-org-apache-sling-servlets-post/pull/6#issuecomment-729744031
Instead of hardcoding to 405, how about making the response status code mappings configurable? For example, look at how the felix healthcheck servlet allows the status codes to be mapped via configuration or request param override for the various scenarios? FYI: There is some precedent for the sling POST servlet to manipulate the response status via the ":status" request parameter, maybe add some enhancements to facilitate more complex status mappings? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
