It was HTTP status200, but turned into sudden timeout so far.
I do not come back to HTTP status 200 in a state of timeout afterwards if it becomes timeout.
Generally, in time for update, I am as follows.
Elapsed time: 5178ms
When perform resend request; HTTP status: It becomes 200.
It wants to prevent it from becoming timeout, how is it all right?
The port has been released, and the practice of the file by the trigger is done, too.
I look forward to hearing from you.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs