Opened 5 years ago

Closed 5 years ago

#4167 closed defect (bug) (fixed)

Huge pagination values break things

Reported by: jonoaldersonwp's profile jonoaldersonwp Owned by:
Milestone: Priority: low
Component: Support Forums Keywords: seo


E.g., take a look at the behaviour of

This, and other extremely high values redirect to a maxint pagination value (e.g.,

This, and other pagination states in the same order of magnitude (e.g., come with some headaches, where they return the 'page 1' state but with incorrect meta values.


All invalid range values should return 404 behaviour, as per low range invalid values do at present (e.g., Related, #4166.

Change History (5)

#1 @dd32
5 years ago

9223372036854775807 is PHP_INT_MAX on a 64bit system, so that's where the redirect is coming from (bbPress is probably using absint() or intval()) is kinda related I think.

While this is also a bbPress problem, it's probably one we can workaround on dotorg without too much issues.

#2 @dd32
5 years ago

In 8224: Force a 404 for any logged out paged requests above MAX_PAGES, this is done to avoid bbPress overriding it later.

See #4167.

#3 @dd32
5 years ago

[8224] covers this for logged out users, is that enough for SEO purposes?

#4 @jonoaldersonwp
5 years ago

Yeah that's super, thanks!

#5 @dd32
5 years ago

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

Cool :) I'm going to close this as fixed then, It's still janky for logged in users, but hopefully if Search engines never index pages like that, users will never end up on a page like that!

Note: See TracTickets for help on using tickets.