[SOLVED] X-Resolve-Urls not working for nested asset

Bugs Solved Bugs
1

I have…

  • [ ] Checked the logs and have provided uploaded a log file and provided a link because I found something suspicious there.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

When X-Resolve-Urls header with value “*” is used. Nested assets dont get resolved.

Expected behavior

When X-Resolve-Urls header with value “*” is used. Nested assets get resolved.

Minimal reproduction of the problem

This is json of schema used:

{
“properties”: {},
“scripts”: {},
“fieldsInLists”: [],
“fieldsInReferences”: [],
“fields”: [
{
“name”: “photos”,
“properties”: {
“fieldType”: “Array”
},
“partitioning”: “invariant”,
“nested”: [
{
“name”: “photo”,
“properties”: {
“fieldType”: “Assets”
},
“parentId”: 1
}
]
}
],
“isPublished”: true
}

Environment

  • [x] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: [latest]

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

2

Thx, makes sense, I have actually never tested this.

3

Hi, I was able to reproduce this. Fix will go out today.

4