There is an issue with the current Importer implementation that results in the path generated on the file system including (incorrectly) any querystring present in the file path. This results in 404 Not Found errors when attempting to retrieve the image.
This results in a 404 error when attempting to retrieve the image in the UI, as it was using the original path as a reference (without the querystring folder):
This PR creates a separate targetPath variable for tracking where the file is stored on the file system, which strips out both the file name and the querystring parameter when verifying the folders.
There is an issue with the current Importer implementation that results in the path generated on the file system including (incorrectly) any querystring present in the file path. This results in
404 Not Found
errors when attempting to retrieve the image.Example:
actor/images/0FKncdMTp0uHEWsy/Ash_Zombie.Avatar.png?1607741617110
.../actor/images/0FKncdMTp0uHEWsy/?1607741617110/Ash_Zombie.Avatar.png
This results in a 404 error when attempting to retrieve the image in the UI, as it was using the original path as a reference (without the querystring folder):
This PR creates a separate
targetPath
variable for tracking where the file is stored on the file system, which strips out both the file name and the querystring parameter when verifying the folders.