# Routing error in 1.2.3, do I need realpath() in all apps?

**URL:** <https://www.ruby-forum.com/t/routing-error-in-1-2-3-do-i-need-realpath-in-all-apps/117232>\
**Category:** Rails\
**Created:** [October 15, 2007, 4:43am UTC](https://www.ruby-forum.com/t/routing-error-in-1-2-3-do-i-need-realpath-in-all-apps/117232 "2007-10-15T04:43:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fxp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/a5b964/32.png) [@fxp](https://www.ruby-forum.com/u/fxp)\
**Post date:** [October 15, 2007, 4:43am UTC](https://www.ruby-forum.com/t/routing-error-in-1-2-3-do-i-need-realpath-in-all-apps/117232/1 "2007-10-15T04:43:58Z")

</div>

I have my applications hosted on a shared server which is running rails  
1.2.3, and I’m having a routing problem. Whenever I try to access one of  
actions I get this error:  
“Routing Error  
no route found to match “/items/list” with {:method=\>:get}”

I googled the error and found that I should add .realpath() to the  
RAILS\_ROOT in boot.rb. Is there a better fix for this, or was it patched  
in a newer version of rails? It seems like I shouldn’t have to edit  
boot.rb for every application that I make.