Send web request - HTTP Status 500

Hello All,

we are trying to send a POST request via "Automation for JIRA" (See screenshot for configuration).
Unfortunately the target server does not process the request as expected but returns HTTP Status 500.

Do you have any ideas what is wrong in our approach?

Best regards,

Daniel

Send web request to enaio.jpg

Error message from the Audit log:

Error publishing webhook. Response HTTP status:
500

Error response HTTP body:
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <title>enaio gateway: Es ist ein Fehler aufgetreten</title> <style> body { background-color: #FFFFFF; font-family: calibri, "sans-serif"; text-align: center; } #main { margin-top: 60px; } </style> </head> <body> <div id="main"> <img src="data&colon;image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAO8AAAAlCAYAAACqA75rAAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH4QIcEgIGtTRpaQAADVFJ

2 answers

0 votes

I am facing the same issue in Jira cloud.

Audit Logs:

Error response HTTP body:

Error publishing webhook. Response HTTP status:500

same thing is working fine with curl

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I'm looking into it tomorrow and will follow-up here once I have something to report. My hope is to find a way to get more information about the failure than what is showing up in the audit log.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

We have something coming "very soon™" that will help in testing outgoing webhooks more thoroughly. Hopefully this will aid in resolving this problem for you. I'll come back with a note when that's shipped to production.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

After putting json in pretty format, it started working.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

@Vikas Sinha I m also trying the same, can you help me out for json format please.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You should be able to test your webhooks now with the built-in test feature, see this comment: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Re-Re-Send-web-request-HTTP-Status-500/qaq-p/1335603/comment-id/67399#M67399

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hi Daniel,

Have you tried hitting the same HTTP endpoint using cURL or another similar tool? I personally find Postman easier to work with.

Unfortunately the audit log doesn't contain enough of the error message to derive anything meaningful from it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

thanks for the answer and sorry for the late reply.

Yes, my colleague tried it with Postman and did not encounter any errors.

The HTTP 500 error still persists when executing the automation rule...

Regards,

Daniel

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I must have a misbehaving filter in my inbox, I didn't see this response until just now.

We've recently rolled out to all Jira Cloud instances so I'll check up on this and see if things are performing as expected. It's after hours here right now but I'll look into it tomorrow and follow-up here once I have something to report.

My hope is to find a way to get more information about the failure than what is showing up in your audit log.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Daniel, We have something coming "very soon™" that will help in testing outgoing webhooks more thoroughly. Hopefully this will aid in resolving this problem for you. I'll come back with a note when that's shipped to production.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Daniel,

We've just added a new feature that allows you to test webhooks from within the "send web request" component configuration. Inserting an issue key or simply hitting "Validate" will send a web request to the webhook URL using the same method that will be used when the automation runs.

This also shows the full request and response payload for the request which should allow you to determine what is going wrong in your request.

Screen Shot 2020-03-31 at 12.16.44 am.png

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This validation step on DC doesn't seem to provide the same set of headers. I got "Content-Length header missing" when using Validate, but no such message during a regular runtime.

It needs testing against a Request bin. I'll get around to that at some point.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Content-Length header error can be fixed easily by adding an optional header

Content-Length = 0

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Product Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Get product advice from experts

Join a community group

Advance your career with learning paths

Earn badges and rewards

Connect and share ideas at events

Send web request - HTTP Status 500

2 answers

Suggest an answer

Was this helpful?

Thanks!

TAGS

Atlassian Community Events