Disallow HTTP methods that are functionally NOT required

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?

1 answer

1 accepted

1 vote

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.

The rest stuff means the remote API + gadgets?

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.

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

384 views 4 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you