Confluence Cloud V2 API Encoding Issue
Incident
Report for Atlassian Developer
Resolved
Apps and consumers of any Confluence Cloud V2 APIs that sent requests containing characters that do not conform to the ISO-8859-1 character encoding standard have been incorrectly encoded and stored within Confluence.
There was no impact to requests that contained the content-type header with a charset=utf-8 directive.
As a result, apps that sent requests while the impact was ongoing might have observed unexpected encoding behaviours.
Here is the timeline of the impact:
- Between 2024-02-09 9:45 & 10:32 PM UTC: the deployment containing the issue was performed
- Between 2024-02-12 11:08 & 11:50 PM UTC, the fix was rolled out to all sites.
All requests now support UTF-8 encoding. This incident is now resolved.
We will run an internal post incident review to fully understand the chain of events that lead to this incident and implement measures to prevent re-occurrence of such incidents in future.
There was no impact to requests that contained the content-type header with a charset=utf-8 directive.
As a result, apps that sent requests while the impact was ongoing might have observed unexpected encoding behaviours.
Here is the timeline of the impact:
- Between 2024-02-09 9:45 & 10:32 PM UTC: the deployment containing the issue was performed
- Between 2024-02-12 11:08 & 11:50 PM UTC, the fix was rolled out to all sites.
All requests now support UTF-8 encoding. This incident is now resolved.
We will run an internal post incident review to fully understand the chain of events that lead to this incident and implement measures to prevent re-occurrence of such incidents in future.
Identified
Starting 2024-02-09 9:45 PM UTC, requests to the Confluence Cloud V2 API containing characters that do not conform to the ISO-8859-1 character encoding standard may have been incorrectly encoded and stored. Please note, the previous and correct encoding is UTF-8.
This incident affected: APIs (Confluence Cloud APIs).