Some long urls that contain spaces like %20 (or other encoded data) are not being saved to the DB faithfully.
take the following url for example:
https://mydocumentsharingplace.net/My%20Storage%20Folder/My%20Shared%20File.txt
gets stored in the shlink database as:
https://mydocumentsharingplace.net/MyStorageFolder/MySharedFile.txt
Which results in being redirected to a 404, because it isnt the same URL.
I suspect the issue is that the longUrl is being encoded and passed as a URI argument through admin-ajax.php as opposed to being sent in the request body as JSON. When I test the same URL using the Shlink web app, the URL is saved in the DB correctly. The shlink webapp accesses the shlink rest API directly.
Some long urls that contain spaces like
%20(or other encoded data) are not being saved to the DB faithfully.take the following url for example:
https://mydocumentsharingplace.net/My%20Storage%20Folder/My%20Shared%20File.txtgets stored in the shlink database as:
https://mydocumentsharingplace.net/MyStorageFolder/MySharedFile.txtWhich results in being redirected to a 404, because it isnt the same URL.
I suspect the issue is that the longUrl is being encoded and passed as a URI argument through
admin-ajax.phpas opposed to being sent in the request body as JSON. When I test the same URL using the Shlink web app, the URL is saved in the DB correctly. The shlink webapp accesses the shlink rest API directly.