#11696 closed defect (bug) (fixed)
canonical redirect isn't working for paged=1
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | Canonical | Version: | |
| Severity: | major | Keywords: | |
| Cc: |
Description
title should be self-explanatory
Change History (9)
comment:2
miqrogroove — 3 years ago
Might be appropriate to pile on or xref with #8948.
comment:3
markjaquith — 3 years ago
- Resolution set to fixed
- Status changed from new to closed
I opened #11857 for paged=too_many
comment:5
follow-up:
↓ 6
miqrogroove — 3 years ago
This is going to cause redirects in empty categories :(
In other words, if I create a category with slug cat1 and put nothing in it, then we now have /category/cat1/page/1/ returning status 302 instead of 404. :(
comment:6
in reply to:
↑ 5
Denis-de-Bernardy — 3 years ago
Replying to miqrogroove:
In other words, if I create a category with slug cat1 and put nothing in it, then we now have /category/cat1/page/1/ returning status 302 instead of 404. :(
That's what #11857 is about. Currently, if you visit /category/cat1/page/100000000 it'll return a status 200.
comment:7
miqrogroove — 3 years ago
If you visit /category/cat1/ it will return a status 200 also. Redirecting from one bogus URL to another doesn't solve the problem.
comment:8
miqrogroove — 3 years ago
Did anyone test this pattern? /tag/slug/&oogabooga/page/1/
comment:9
miqrogroove — 3 years ago
Also what about? /yyyy/mm/slug/page/0/
paged=$too_much is also broken. it should return a 404 error, or maybe 301 redirect to the first page.