Proxy error in development and staging when calling Confluence attachments API with requestConfluence

Forge
, , ,
1

We’ve started seeing the following error in the development and staging environments (production is fine) when calling the Confluence attachments API with requestConfluence:

message: 'Forge platform failed to process runtime HTTP request - 400 - INVALID_TARGET_URL',
name: 'PROXY_ERR',
status: 400

The code triggering this (which runs fine in production):

const response = await api.asUser().requestConfluence(route`/wiki/rest/api/content/${pageId}/child/attachment/${imgId}/download`, {
    headers: {
        'method': 'HEAD'
    }
});

Has anyone encountered something similar and/or have any suggestions on how to debug further?

Thanks

1 Like
2

Hi @Judd !

To help us investigate, could you please share your app ID and the approximate timestamp of when you received this error? Also, if the error context includes a request ID or trace ID, that would also be helpful.

1 Like
3

This was caused by a networking change and has been rolled back - if you try again now things should be working.

We identified approximately 9 apps would have experienced this error.

4

Thanks @HeyJoe! Works now. Cheers for the fast fix! Much appreciated :slight_smile:

5

Hi,

I am developing an app and getting the same response on all routes I tried with requestBitbucket()
I tried wit many routes
Do you know if the issue is happening again?

Update:
I also tried in another app on jira, with requestJira and the same issue, the app is in development, I have no production environment yet