WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#11696 closed defect (bug) (fixed)

canonical redirect isn't working for paged=1

Reported by: Denis-de-Bernardy Owned by: markjaquith
Milestone: 3.0 Priority: normal
Severity: major Version:
Component: Canonical Keywords:
Focuses: Cc:
PR Number:

Description

title should be self-explanatory

Change History (9)

#1 @Denis-de-Bernardy
10 years ago

paged=$too_much is also broken. it should return a 404 error, or maybe 301 redirect to the first page.

#2 @miqrogroove
10 years ago

Might be appropriate to pile on or xref with #8948.

#3 @markjaquith
10 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [12691]) Do proper canonical redirect for ?paged=1 or /page/1/. fixes #11696

#4 @Denis-de-Bernardy
10 years ago

I opened #11857 for paged=too_many

#5 follow-up: @miqrogroove
10 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. :(

#6 in reply to: ↑ 5 @Denis-de-Bernardy
10 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.

#7 @miqrogroove
10 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.

#8 @miqrogroove
10 years ago

Did anyone test this pattern? /tag/slug/&oogabooga/page/1/

#9 @miqrogroove
10 years ago

Also what about? /yyyy/mm/slug/page/0/

Note: See TracTickets for help on using tickets.