Thanks a lot. I am very sorry. I was in the mode to make things more consistent and did not pay attention on that. In general this is something I would like to remove in the not so far future.
But the result is just the asset ID (which is known) and the app name (which is usually static), so there is no extra information that you would have to pull.
This is true, but when we have pages with different “component” schemas injected into the page we then have to either loop through all the components, check for images then compile those accordingly. Or perhaps create a general regex or something to mass replace.
At the time, using X-ResolveUrls was much easier and efficient since we don’t need to do any compiling on the backend before sending to the frontend.
Either way, the root issue here is that a production feature was changed without warning or documentation or creating backwards combability.
We are slowly converting our projects to GraphQL, but please update if you plan to remove the X-ResolveUrls because we will have re-work how we process assets.
Keep us updated for future changes to this header