Routing

2 views
Skip to first unread message

Frisco Del Rosario

unread,
Nov 19, 2010, 3:25:10 AM11/19/10
to dojo-ruby-on-rails
After config/routes.rb is edited with

root :to => "salute#hello"

Why does localhost/salute/hello return a routing error?

Scott Haines

unread,
Nov 19, 2010, 5:56:39 PM11/19/10
to dojo-ruby...@googlegroups.com
Frisco,

or were you putting localhost/salute/hello into the url?
--
Scott Haines
Founder / Creative Director / Lead Architect
Newfront Creative LLC
P 408.905.8473 C 408.705.7833
http://www.newfrontcreative.com
http://www.twitter.com/newfront

Frisco Del Rosario

unread,
Nov 19, 2010, 11:05:15 PM11/19/10
to dojo-ruby-on-rails
The URL was correct.

Bigger problems at the moment. MySQL isn't creating a socket at
startup.

On Nov 19, 2:56 pm, Scott Haines <sc...@newfrontcreative.com> wrote:
> Frisco,
> is your urlhttp://localhost:3000/salute/hello
>
> or were you putting localhost/salute/hello into the url?
>
> On Fri, Nov 19, 2010 at 12:25 AM, Frisco Del Rosario <
>

Frisco Del Rosario

unread,
Nov 20, 2010, 8:18:03 PM11/20/10
to dojo-ruby-on-rails
I've found that generating the scaffold before generating models or
controllers set things straight.

I don't understand why.

Scott Haines

unread,
Nov 22, 2010, 1:10:06 PM11/22/10
to dojo-ruby...@googlegroups.com
Frisco,
Typically the issue will stem back to the route type. I will be going over get / post / put / delete CRUD tonight, basically the routing can block certain types of page requests.

get "controller/action" will accept get parameters, but won't accept post variables from page to page

post "controller/action" will only accept post parameters inbound from a form or another outlet, this helps to further control the application based on security measures. It is also a pain to get used to!
Reply all
Reply to author
Forward
0 new messages