Action 'HTTP_2' failed_Status Code 302

(0) Share

Report

Posted on by THPR1996

I am getting Status code 302 in HTTP2 Connector.

I am getting data from shared mail box and the FireEye link embedded with in the image.

while I'm passing this embedded fire eye link in HTTP2 connector I'm getting 302 error.

May I know what could be the reason?

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Expiscornovus 33,189 Most Valuable Professional on at

Like (0)

Report

Hi @THPR1996,

HTTP 302 responses are used a lot to redirect. So, it is pretty likely that in the response of the HTTP 2 action you received another hyperlink which you can use to navigate to.

Can you check if you can see a second link in the outputs (there might be a location field in the response headers)?

Was this reply helpful? Yes No
THPR1996 2 on at

Like (0)

Report

Yes I can see the location field in the response headers and the link is opening as well as downloading the image in my local. But not sure why the HTTP2 trigger failing. Its not showing what kind of error it is.Seems this is the first time we are getting this kind of issue. Is there any alternative to achieve this? Because i need to pass that HTTP2 trigger body to file content where i am uploading the image in a document library

Was this reply helpful? Yes No
Expiscornovus 33,189 Most Valuable Professional on at

Like (1)

Report
Hi @THPR1996,

You could use a condition action to check the status code. Make sure you configure the run after setting to has failed. Within the If Yes section you could use another HTTP action and use the Location value to navigate to the actual location (redirected).

Below is an example setup.

The URI field of the HTTP 3 action uses this expression:

actions('HTTP_2').outputs.headers.Location

The condition is configured with the configure run after setting. (that's why you see the red dotted arrow between the HTTP 2 and Condition actions)

Was this reply helpful? Yes No
Shaheer Ahmad 2,194 Moderator on at

Like (0)

Report

I am experiencing this issue after adding another http action from the location url:

Note: It's working fine in postman:

Was this reply helpful? Yes No