It looks like the Editor.js feature is hard coded to connect to an API endpoint that doesn't prepend the directories with the nested IIS directory name(s). Example Nested Site URL: https://hostname.domain[.]com**/$NestedAppDirectory**/
Expected behavior
Editor.js should post to: https://hostname.domain[.]com/$NestedAppDirectory/api/internal/component/editor/image/$PublicFolderName
Actual behavior
Editor.js posts to: https://hostname.domain[.]com/api/internal/component/editor/image/$PublicFolderName
This results in a 404 error being returned.
Version
4.3.1
Severity
Low
Environment
Nested IIS
Steps to Reproduce
It looks like the Editor.js feature is hard coded to connect to an API endpoint that doesn't prepend the directories with the nested IIS directory name(s). Example Nested Site URL: https://hostname.domain[.]com**/$NestedAppDirectory**/
Expected behavior
Actual behavior
Additional Environment data
No response
Screenshots/Animations
No response