i think you should add a record in you routes.rb file that includes the page, for example:
map.connect 'archive/:id', :controller => 'articles', :action => 'list', :page => 1 map.connect 'archive/:id/:page', :controller => 'articles', :action => 'list' these rows do on more thing, they change the url to: "/archive/id", "/ results/id/2"... which is good because then you can use page cache for your pagination, if you would like to keep the &page=.. you can do that simply by changing the first parameter to fit your needs. in addition, believe that 301 redirect even though it's a bad solution solve the problem for search engines as well, in that case it's must be 301 and the reason i think it's bad is because one request becomes two and it slows things down for the client and the server. On Mar 29, 6:03 am, Aldo Italo <rails-mailing-l...@andreas-s.net> wrote: > i have noted a problem in will_paginate : > > In a pagination, when go to pages geather than 1 value thath' ok, but if > you back to page 1 in the URL appear the parameter page=1 > this is bad for seo optimization, because engine view same page with > diffent URL. > how can remove the param only for the first page? > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
