Handling encoded paths like @s3bucket/_small/my%20spaced%20file.jpg

[jakenuts]

Updated the uri_omitted_origin to use a 'raw_uri' instead of $uri which is normalized by default and results in no request to imgproxy.

##! **`$raw_uri`**
## Create a raw_uri from the un-decoded request URI
##  $uri is the decoded path with no query string
##  $request_uri is the original path including the query string
## Here we remove the query string from the non-decoded $request_uri
map $request_uri $raw_uri
{
    default '$request_uri';
    ~^([^?]*) $1;
}

##! **`$uri_omitted_origin`**
## Get the URI after omitting origin server.
## This setup assumes that an origin server starts with an `@` symbol.
map $raw_uri $uri_omitted_origin
{
    default '$raw_uri';
    ~^(/@[^/]+)?(?<parsed_path>/.+)$        '$parsed_path';
}

[shinsenter]

Hi @jakenuts,

Thank you so much for reaching out and suggesting improvements for this project.

My aim with this project is to provide a basic set of configurations so that anyone can easily set up a personal image processing server. Since most common HTTP requests don't contain special characters, I assumed that file URLs wouldn't have %-encoded special characters.

Unfortunately, I haven't had the chance to test the code you're proposing with %-encoded characters other than "%20". Handling special characters could make the configuration more complex than simply renaming files or adding rewrite rules, which is why I'm hesitant to incorporate your idea into the Nginx config at this stage.

However, I really appreciate your contribution. If this change suits your project, please feel free to clone my repository and customize it as needed. Thank you once again for your valuable suggestion and understanding!

Best regards,

[jakenuts]

Totally understand, thanks. Just having the Github issue for reference if other users run into the problem in the future should be fine. Thanks!

[shinsenter]

Hey @jakenuts

I made some changes to the Nginx configuration based on your suggestion: Apply suggestion in #17

Please help me pull this repository and test if it works as you expect.