Update LastModified date format to ISO string in XML response#6085
Update LastModified date format to ISO string in XML response#6085bert-e merged 2 commits intodevelopment/9.3from
Conversation
Hello ziyanglinscality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
This comment was marked as resolved.
This comment was marked as resolved.
391b803 to
adc7c94
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 3 files with indirect coverage changes @@ Coverage Diff @@
## development/9.3 #6085 +/- ##
===================================================
- Coverage 84.31% 84.26% -0.05%
===================================================
Files 206 206
Lines 13251 13251
===================================================
- Hits 11172 11166 -6
- Misses 2079 2085 +6
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
DarkIsDude
left a comment
There was a problem hiding this comment.
We should have test somehow 🙏
anurag4DSB
left a comment
There was a problem hiding this comment.
Lets add the test and then we should be good.
Add a regression test that captures the XML body from the LIST route and verifies all LastModified values match ISO 8601 format, preventing the RFC 2822 date format bug from recurring.
4f11a1f to
6002c51
Compare
|
/approve |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the The following options are set: approve |
|
/status |
StatusStatus report is not available. The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
Queue build failedThe corresponding build for the queue failed:
Remove the pull request from the queue
|
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-857. Goodbye ziyanglinscality. |
Issue CLDSRV-857
When browsing objects created by Veeam SOSAPI, the UI shows "An error occurred while loading data" even though the API returns a 200 response with valid XML.
Root cause: The LastModified field in the response uses RFC 2822 format (Mon, 23 Feb 2026 08:24:20 GMT) instead of ISO 8601 (2026-02-23T08:24:20.000Z). AWS SDK v3 strictly expects RFC 3339/ISO 8601 and throws TypeError: Invalid RFC3339 timestamp format during deserialization, causing the entire response to fail.