Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,655
Community Members
 
Community Events
176
Community Groups

Error when calling Jira API

"Bad Chunk Size" error when other platform calling Jira API. The Jira issue key didn't reply to the platform. Is there anyone who knows about this?

1 answer

1 accepted

0 votes
Answer accepted
Charlie Misonne Community Leader Jun 15, 2022

Hi Jason,

Can you post an example of the REST call you are executing including its headers?

Hi Charlie, I just got the REST call. It's /rest/api/2/issue/ 

Head:

<html>

<head>
<title>Forbidden (403)</title>

 

<!--[if IE]><![endif]-->
<script type="text/javascript">
(function() {
var contextPath = '';
var eventBuffer = [];

function printDeprecatedMsg() {
if (console && console.warn) {
console.warn('DEPRECATED JS - contextPath global variable has been deprecated since 7.4.0. Use `wrm/context-path` module instead.');
}
}

function sendEvent(analytics, postfix) {
analytics.send({
name: 'js.globals.contextPath.' + postfix
});
}

function sendDeprecatedEvent(postfix) {
try {
var analytics = require('jira/analytics');
if (eventBuffer.length) {
eventBuffer.forEach(function(value) {
sendEvent(analytics, value);
});
eventBuffer = [];
}

if (postfix) {
sendEvent(analytics, postfix);
}
} catch(ex) {
eventBuffer.push(postfix);
setTimeout(sendDeprecatedEvent, 1000);
}
}

Object.defineProperty(window, 'contextPath', {
get: function() {
printDeprecatedMsg();
sendDeprecatedEvent('get');
return contextPath;
},
set: function(value) {
printDeprecatedMsg();
sendDeprecatedEvent('set');
contextPath = value;
}
});
})();

Hi Charlie, could you help to check? If you need anything, please let me know. Thank you so much.

Charlie Misonne Community Leader Oct 17, 2022

Hi Jason,

I don't think I really understand what you're dealing with exactly.

I missed the part where you said "other platform". Do you see the "bad chunk size" in the UI of that other platform?
Can you post a screenshot?

I also found this related bug report. Perhaps it is related to your issue.

https://jira.atlassian.com/browse/JSWSERVER-20190

微信截图_20221017154356.png

Hi Charlie, it's like this. 

Hi Charlie, we also met some other errors, such as 405 when using automation calling. But manually calling the API to create Jira issue succeeded. Is there any unstable system reason or else?微信截图_20221017155910.png

Charlie Misonne Community Leader Oct 17, 2022

Hi Jason,

What do you mean with "automation calling"? I don't understand how you are making those http requests. if they are being made by another program I assume that program is not properly creating the requests.

405 response means: method not allowed. For example: doing a GET when it should be a POST.

Bad chunk size: could be a bug like https://jira.atlassian.com/browse/JSWSERVER-20190 or a very large request that can't be handled by Jira.

Thank you Charlie for your information. We will take a look on it.

Hi Charlie, do you know 400 error generally means what?

Charlie Misonne Community Leader Oct 20, 2022

Hi Jason,

An http 400 response meanse "bad request". It means that the request is malformed or contains something that the target can not process. In other words: the error is usually on the client side.

Thank you so much, Charlie.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.2
TAGS

Atlassian Community Events