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
Comment #1
Dave ReidThe module is all about redirections. This is the 'redirect' front page path to actual front page (no path specified). Why isn't it acceptable?
Comment #2
nicholasThompsonNo 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.
Comment #3
jcisio CreditAttribution: jcisio commentedCan 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...