I'm finding that GR is doing a 301 redirect of the additional blog listing pages. For example, when I mouse over the next page link in the pager at the bottom of the front page, the link is http://example.com/node?page=1 but when I click on it, the redirect is http://example.com/?page=1 (it strips the word node). The page loads as expected, but I really don't think this redirect is expected or acceptable behavior for the module.
I tried various settings in the module, but nothing changed. The only thing that fixed it was to disable GR.

BTW, I know the redirect is 301 because a site analysis from http://validator.w3.org/checklink reported it as something to fix.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Postponed (maintainer needs more info)

The module is all about redirections. This is the 'redirect' front page path to actual front page (no path specified). Why isn't it acceptable?

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

No reply for 2 months. Cheers for replying Dave.

fred0 - This is, as Dave said, expected and appropriate behaviour as node is actually the default frontpage listing. GR is saving you from duplicate content.

jcisio’s picture

jcisio commented
Status: Closed (works as designed) » Active

Can this module modify pager (and maybe all generated urls) so that no redirect is needed at all? Currently when I am at /node, I am redirected to /, but all links in pager keep to be /node?page=1, /node?page=2...