The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can you prevent the "Send web request" action following 303/302 Redirects

Steve King
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 22, 2024

Hi team,

I've setup an automation that makes a web request for a custom value - the request works almost perfectly. The expected behavior is:

  1. Send GET web request successfully completes the request.
  2. The Web Server provides a Status: 303, and a Header: Location: https://new.url.here/ is returned
  3. {{webResponse}} should provide the headers above and {{webResponse.status}} should be 303 and {{webResponse.statusCategory}} should also return REDIRECT

Actual behavior is that web request continues to follow the 303/Location redirect and returns the redirected content and headers.

This is also true when "web request" is set to "HEAD" instead of GET. The backend goes on and follows the redirect - as per the screenshot.

Screenshot 2024-08-23 at 2.44.20 AM.png

Does anyone have any tips on preventing this? Or how to access the first set of headers instead of the final redirected set?

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events