You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a filename contains a question mark (?) pigallery2 will not be able to display the picture. For example if there are identical and valid jpg files main_page.jpg and main_page?.jpg then, the former will be shown correctly, while the latter will not be shown.
Photo/video (optional) that causes the bug
independent of picture
Screenshots (optional)
^ illustration
Server logs (optional)
6/8/2022, 7:38:05 PM[VERBS] GET /api/gallery/content/test/main_page?.jpg/thumbnail/480 404 2ms
Note that requesting manually with %3F instead of ? works :
6/8/2022, 7:39:22 PM[VERBS] GET /api/gallery/content/test/main_page%3F.jpg/thumbnail/480 200 59ms
Environment (please complete the following information):
OS: linux server, Ubuntu 20.04
Browser macOS, Chrome
Used app version:
Using Docker, but I'm struggling to get the version out. It is the current latest. If you advice how to get the version number, I'll extract it. Until then, I found this in the logs:
Searching through the logs, it seems that spaces are being converted correctly to %20 on the URL, but the ? remain as such. Manually correcting the url to convert ? to %3F fixes the URL.
Describe the bug
If a filename contains a question mark (
?
) pigallery2 will not be able to display the picture. For example if there are identical and valid jpg filesmain_page.jpg
andmain_page?.jpg
then, the former will be shown correctly, while the latter will not be shown.Photo/video (optional) that causes the bug
Screenshots (optional)
^ illustration
Server logs (optional)
Note that requesting manually with
%3F
instead of?
works :Environment (please complete the following information):
Used app version:
Using Docker, but I'm struggling to get the version out. It is the current
latest
. If you advice how to get the version number, I'll extract it. Until then, I found this in the logs:The text was updated successfully, but these errors were encountered: