Hi,
I have two environment (A and B). Environment A stores the file attachments on a windows drive. Environment B stores the file attachments on a NAS (Network Attached Storage).
When a file with a '=' sign is uploaded, the URL for the file is encoded as below:-
Test%beProd.txt
The above is wrong, since the encoding corresponding to '=' is '%3D'. But anyways, that is not the problem. When trying to view the file, I am able to view the file in Environment A and not on Environment B. Environment B gives an internal server error when trying to view the file. The decoding of the path of attachment is happening as below:
On Env A:-
Test3/4Prod.txt
On Env B:-
Test¾Prod.txt
As you can see, there is a difference between the 3/4. In Environment B, the '%be' is being decoded as ¾. If I change this value on the URL to '3/4', I am able to view the file.
I have tried a lot of different things but nothing seems to work. Has anyone faced such a weird issue before? Any help is much appreciated.
Thanks.
I have two environment (A and B). Environment A stores the file attachments on a windows drive. Environment B stores the file attachments on a NAS (Network Attached Storage).
When a file with a '=' sign is uploaded, the URL for the file is encoded as below:-
Test%beProd.txt
The above is wrong, since the encoding corresponding to '=' is '%3D'. But anyways, that is not the problem. When trying to view the file, I am able to view the file in Environment A and not on Environment B. Environment B gives an internal server error when trying to view the file. The decoding of the path of attachment is happening as below:
On Env A:-
Test3/4Prod.txt
On Env B:-
Test¾Prod.txt
As you can see, there is a difference between the 3/4. In Environment B, the '%be' is being decoded as ¾. If I change this value on the URL to '3/4', I am able to view the file.
I have tried a lot of different things but nothing seems to work. Has anyone faced such a weird issue before? Any help is much appreciated.
Thanks.