Non-existent ?page parameter doesn't redirect/404

(Fred Kelly) #1


We are noticing that duplicate pages have started being indexed by Google, for example:

curl -I -L
=> HTTP/1.1 200 OK

=> HTTP/1.1 200 OK

Ideally the latter (non-existent) URL should 404 or redirect, it seems the current behaviour is to render the correct (former) URL, but with a status 200 (unless I’m mistaken).

This is running v0.9.9.9, though I notice the same behaviour is present on which I assume is running a newer release.

Any help appreciated; apologies if there is an obvious solution.

(Sam Saffron) #2

putting this down as a bug, we should be 404ing stuff that is out of range.

(Sam Saffron) #3

Just committed a fix for this:

(Jeff Atwood) #4