Bug Report: 404 Error for URLs without Extensions #13
-
Summary: Steps to Reproduce:
Expected Behavior:
Actual Behavior:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Thank you for your interest and for reaching out my project. Regarding the issue you are raising, I will guide you on how to customize the Nginx settings to be able to handle more specialized URL patterns that you desire. This is not a bug, as this project is not an image processing program itself, but rather a collection of settings to allow many people to easily set up their own image processing server. This project only provides very basic configurations, and of course to serve other requirements, you need to customize it. In the variable declaration section for ## **`$use_imgproxy`**
## This flag indicates that the request will be proceeded by `imgproxy`.
map $uri $use_imgproxy
{
default 0;
# files under the `/item_image/` path are images and should also be processed
#> E.g. /item_image/abc is an image
~^/item_image/ 1;
# or process all image files with these file extensions
~*\.(jpe?g|png|gif|tiff?|bmp)$ 1;
} Of course, you can also use more complex regular expressions to filter the paths exactly according to your requirements. I wish you success in setting up your own image processing system. If you find this project useful, consider donating via PayPal or sharing it with your friends. Your support helps keep this project maintained and improved for the community. Best regards |
Beta Was this translation helpful? Give feedback.
@naveenrao2k
Thank you for your interest and for reaching out my project.
Regarding the issue you are raising, I will guide you on how to customize the Nginx settings to be able to handle more specialized URL patterns that you desire. This is not a bug, as this project is not an image processing program itself, but rather a collection of settings to allow many people to easily set up their own image processing server. This project only provides very basic configurations, and of course to serve other requirements, you need to customize it.
In the variable declaration section for
$use_imgproxy
in theimgproxy.conf
file (here), you can add a rule so that Nginx knows that files under the/ite…