fix: update redirect logic for URLs ending with '/'#2255
fix: update redirect logic for URLs ending with '/'#2255bjohansebas wants to merge 6 commits intonextfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next #2255 +/- ##
==========================================
+ Coverage 95.67% 95.70% +0.02%
==========================================
Files 13 13
Lines 901 907 +6
Branches 263 267 +4
==========================================
+ Hits 862 868 +6
Misses 39 39 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
friendly ping @alexander-akait |
| filename = path.join( | ||
| outputPath, | ||
| pathname.slice(publicPathPathname.length), | ||
| index || "", |
There was a problem hiding this comment.
I think we need better logic here, because our logic to search index below, so I think we should split it, i.e. like we have in the send package, if it is ends on / we need to apply this logic, otherwise no, right now we just mix this logic
There was a problem hiding this comment.
We’re already doing it :)
There was a problem hiding this comment.
@bjohansebas hm, I always thought that our logic is different here, I will look deeply tomorrow
There was a problem hiding this comment.
Not so much in the PR description, there’s a bit about how send implements this functionality.

Summary
Okay, this took me a bit of time to understand. This is something similar to what send does. After several attempts, it can probably be refactored even more, but this would be the main solution.
The send workflow is: if it detects a trailing slash at the end of pathname ("/") (line of code), then it goes into another code path, where it joins the original pathname and appends the index (line of code which is configurable, just like in this package). When they are joined, if such an index file exists, it continues with the normal workflow, otherwise, it throws an error, similar to what is handled here. The difference is that now, if there is a trailing slash, the index file (which is configurable) is also appended
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
yes!
If relevant, what needs to be documented once your changes are merged or what have you already documented?