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: 

Broken SPACES API after upgrade

Albi Gjino
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!
January 27, 2024

We upgraded from Confluence 6.13 to 7.9.18 by performing a second installation of Confluence and importing the database. When logging in and trying to access the list of spaces through the "Spaces DIrectory" link it says "An error occurred while searching for spaces."

After debugging the issue, I noticed that the UI is sending an AJAX request to the backend and getting XML as response, but it tries to parse it as JSON and errors out. The  request header is actually for JSON, but the backend returns XML. HEADER ACCEPT is "application/json, text/javascript, */*; q=0.01"

What part of the upgrade process could have caused this, and what can I try to make the backend return JSON?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Albi Gjino
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!
January 27, 2024

It turns out the problem was in AWS CloudFront. CloudFront wasn't forwarding the headers and therefore the ACCEPT header wasn't going to the backend, which was defaulting to XML. I added the headers to the Cache Key in CloudFront Behavior and now it works fine.

TAGS
AUG Leaders

Atlassian Community Events