[ https://issues.apache.org/jira/browse/TIKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343373#comment-14343373 ]
Sergey Beryozkin commented on TIKA-891: --------------------------------------- Just to clarify: I've no objections to migrating to POST from PUT, I guess neither fits perfectly, perhaps POST is marginally 'cleaner', but ultimately is is not that important IMHO :-). The question is how to support the existing users. Keeping PUT for 1.8 only might make sense. I guess it depends on whether 1.8 is considered a major version or not Thanks > Use POST in addition to PUT on method calls in tika-server > ---------------------------------------------------------- > > Key: TIKA-891 > URL: https://issues.apache.org/jira/browse/TIKA-891 > Project: Tika > Issue Type: Improvement > Components: general > Reporter: Chris A. Mattmann > Assignee: Chris A. Mattmann > Priority: Trivial > Labels: newbie > Fix For: 1.8 > > > Per Jukka's email: > http://s.apache.org/uR > It would be a better use of REST/HTTP "verbs" to use POST to put content to a > resource where we don't intend to store that content (which is the > implication of PUT). Max suggested adding: > {code} > @POST > {code} > annotations to the methods we are currently exposing using PUT to take care > of this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)