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
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.