Disallow HTTP methods that are functionally NOT required

[Sameera Shaakunthala [inactive]]

As a security measure, we are thinking of disallowing all the HTTP methods on our JIRA instance except the functionally required ones. The required HTTP methods at the moment I can think of are GET and POST.

Is there any functional impact if we disallow methods other than GET and POST?

[JamieA · Accepted solution]

Don't do this without fully understanding jira. The rest stuff uses PUT and DELETE for example. If for instance you restrict to get and post you will not be able to update roles in jira.

[Sameera Shaakunthala [inactive]]

The rest stuff means the remote API + gadgets?

[Nic Brough -Adaptavist-]

Some of the internal servlets use REST, as well as the external API and gadgets.

I really wouldn't do this without significant testing of every function in the UI, especially the admin side of it.

[Sameera Shaakunthala [inactive]]

REST is not a HTTP method defined in the RFC 2616. REST is actually HTTP GET, isn't it?

[JamieA]

No... see https://en.wikipedia.org/wiki/Representational_state_transfer