Added shortcuts via RewriteRule to .htaccess

[nagmat84]

While I was looking for a solution to #1217 (comment), I discovered that our .htaccess could be improved.

As there is a lot (I mean really A LOT) requests for the upload directory, we can take a shortcut there. The new rules also avoid some unnecessary exceptions and logging, if a browser requests a non-existing file.

[codecov]

Codecov Report

Merging #1272 (af88ee1) into master (760839b) will decrease coverage by 0.96%.
The diff coverage is n/a.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[nagmat84]

While I was working on the .htaccess file, I also wondered if these lines

Lychee/public/.htaccess

Lines 12 to 15 in 4d1b5f0

	# Redirect Trailing Slashes If Not A Folder...
	RewriteCond %{REQUEST_FILENAME} !-d
	RewriteCond %{REQUEST_URI} (.+)/$
	RewriteRule ^ %1 [L,R=301]

are actually correct. Here, %1 in the RewriteRule captures everything of the URL but the trailing /, then the RewriteRule replaces the beginning of the URL ^ by %1. The value of %1 is put it front of the URL which is already there, i.e. if my-url/ is not an existing directory, then the browser is redirected to the URL my-urlmy-url/. I don't think this is intended, and the rule should be RewriteRule .* %1 [L,R=301].

Why do we need the rules at all? What purpose do they serve? @ildyria added them to .htaccess.

[ildyria]

I never touched that part of the file.
C.f. original here: https://github.com/laravel/laravel/blob/9.x/public/.htaccess

[ildyria]

Tested. LGTM.