I ran into this while trying to debug an issue with the Jira Issue community plugin.
Our jira server is set up so when making some requests, like getting a users’s avatar, the flow is to request the URL for avatar, get a 30x response with several ‘set-cookie’ headers in the response, then call new URL from the 30x with the new cookies set in the request.
I can do this from curl or other tools, and browsers to The Right Thing by setting the cookies in subsequent requests, but Obsidian does not.
The ‘requestUrl’ call does not have a way to insert the cookies into the redirect as everything is hidden behind the first call, and the ‘requestUrl’ call doesn’t do the cookie setting for us.
Is there a way to either short-circuit the requestUrl call on certain status, to get the requestUrl to do the cookie setting for us, or ???
Thanks!