PUT Rest API return 'internal server error'

Kan Zhang August 25, 2013

Hi all:

I was using the PUT rest API to update an issue using the admin user, I always got the 'internal server error'. however, when i tried the same operation on a testing server, it is all right. the first server is Linux and the testing server is windows xp.

the response header of hte linux is :

-Headers{X-AREQUESTID: 855x278060x2

X-Seraph-LoginReason: OK

Set-Cookie: JSESSIONID=F2A596317664196D13FD2C1F1EE0BE0C; Path=/; HttpOnly,atlassian.xsrf.token=AHPB-JEL2-VI9D-ZA05|129fa57893ffb65cda6d6e6c90917c2cd11e5a64|lin; Path=/

Server: Apache-Coyote/1.1

X-AUSERNAME: admin

Cache-Control: no-cache, no-store, no-transform

Content-Type: application/json;charset=UTF-8

Transfer-Encoding: chunked

Date: Mon, 26 Aug 2013 06:15:23 GMT

Connection: close

}System.Net.WebHeaderCollection

whereas the windowsxp response header looks like :
-Headers{X-AREQUESTID: 856x33886x1
X-Seraph-LoginReason: OK
Set-Cookie: JSESSIONID=854220691DC3975B5102E3A93FCF9288; Path=/; HttpOnly,atlassian.xsrf.token=AHPB-JEL2-VI9D-ZA05|adfa98891f886695e389da3f25e6d84b92f4e978|lin; Path=/
Server: Apache-Coyote/1.1
X-AUSERNAME: admin
Date: Mon, 26 Aug 2013 06:16:06 GMT
Connection: close
}System.Net.WebHeaderCollection
Any suggestions???
Thanx in advance!!!

2 answers

1 accepted

1 vote
Answer accepted
Kan Zhang August 26, 2013

Thanks Lucas,

i v found the problem, it was a plugin issue: the linux application has a risk management plugin which introduces a custom field that caused the problem when 'put issue' is called

0 votes
LucasA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 25, 2013

Hi Kan,

Since the REST API command is working from a remote box, I'm thinking about an environment problem. Have you used cURL to perform the call? Hence, can you confirm if you haven't any firewall running on the server? Can you also try to set the JIRA BaseURL (Administration -> General Configuration) to http://localhost:8080 just for testing and, then, repeat the cURL command?

Best regards,
Lucas Timm

Suggest an answer

Log in or Sign up to answer