REFUSED_STREAM (err 7) occurs when using REST API to create JIRA issue

Kyungyeong Lee July 20, 2016

Below error is responded to the shell when I executed the command line to create JIRA issue using REST API.

REFUSED_STREAM.jpgtest_txt.jpg

What does that mean ?
What should I check more in order to create issue without error ?
The command is just copied from the tutorial page https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis and I modified it with my project information.

1 answer

1 accepted

0 votes
Answer accepted
Petar Petrov (Appfire)
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.
July 20, 2016

For some reason curl is using HTTP/2. I don't think the Tomcat version supplied with JIRA supports that. Try adding the --http1.1 command line option. 

Kyungyeong Lee July 20, 2016

Thank you for the comment.

Response is changed, but I still don't get an expected result and I don't know what that means.

resp1.jpgresp.JPG

Petar Petrov (Appfire)
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.
July 20, 2016

Your URL is incorrect - the server return 404. Are you sure you have "/jira" in the context path? Use the "-v" option for CURL to see verbose logs.

Kyungyeong Lee July 21, 2016

You are correct.   I finally got that resolved after removing "/jira" from ~/jira/rest/api/2/issue. I got confused because the tutorial page that contains "/jira".

But most of all --http1.1 is also really helpful. It seems that it is required when sending request using curl. Thank you so much.

Petar Petrov (Appfire)
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.
July 21, 2016

Cool, glad to help. There is an interesting excerpt in the cURL documentation that explains what you see:

Since 7.47.0, the curl tool enables HTTP/2 by default for HTTPS connections.

Suggest an answer

Log in or Sign up to answer