debugging - Enigmatic GET request from Rails app -


i seeing strange thing, when run server rails app. log:

jatins-macbook-pro: silverspoon$ rails s => booting thin => rails 3.2.8 application starting in development on http://0.0.0.0:3000 => call -d detach => ctrl-c shutdown server >> thin web server (v1.5.0 codename knife) >> maximum connections set 1024 >> listening on 0.0.0.0:3000, ctrl+c stop   started "/app/update-progress" 127.0.0.1 @ 2013-05-19 15:04:56 +0530 connecting database specified database.yml  actioncontroller::routingerror (no route matches [get] "/app/update-progress"):   actionpack (3.2.8) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'   actionpack (3.2.8) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'   railties (3.2.8) lib/rails/rack/logger.rb:26:in `call_app'   railties (3.2.8) lib/rails/rack/logger.rb:16:in `call'   actionpack (3.2.8) lib/action_dispatch/middleware/request_id.rb:22:in `call'   rack (1.4.1) lib/rack/methodoverride.rb:21:in `call'   rack (1.4.1) lib/rack/runtime.rb:17:in `call'   activesupport (3.2.8) lib/active_support/cache/strategy/local_cache.rb:72:in `call'   rack (1.4.1) lib/rack/lock.rb:15:in `call'   actionpack (3.2.8) lib/action_dispatch/middleware/static.rb:62:in `call'   railties (3.2.8) lib/rails/engine.rb:479:in `call'   railties (3.2.8) lib/rails/application.rb:223:in `call'   rack (1.4.1) lib/rack/content_length.rb:14:in `call'   railties (3.2.8) lib/rails/rack/log_tailer.rb:17:in `call'   thin (1.5.0) lib/thin/connection.rb:81:in `block in pre_process'   thin (1.5.0) lib/thin/connection.rb:79:in `catch'   thin (1.5.0) lib/thin/connection.rb:79:in `pre_process'   thin (1.5.0) lib/thin/connection.rb:54:in `process'   thin (1.5.0) lib/thin/connection.rb:39:in `receive_data'   eventmachine (1.0.1) lib/eventmachine.rb:187:in `run_machine'   eventmachine (1.0.1) lib/eventmachine.rb:187:in `run'   thin (1.5.0) lib/thin/backends/base.rb:63:in `start'   thin (1.5.0) lib/thin/server.rb:159:in `start'   rack (1.4.1) lib/rack/handler/thin.rb:13:in `run'   rack (1.4.1) lib/rack/server.rb:265:in `start'   railties (3.2.8) lib/rails/commands/server.rb:70:in `start'   railties (3.2.8) lib/rails/commands.rb:55:in `block in <top (required)>'   railties (3.2.8) lib/rails/commands.rb:50:in `tap'   railties (3.2.8) lib/rails/commands.rb:50:in `<top (required)>'   script/rails:6:in `require'   script/rails:6:in `<main>'  rendered /users/silverspoon/.rvm/gems/ruby-1.9.3-p194@fbtracker/gems/actionpack-3.2.8/lib/action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (2.3ms) 

and, request made repeatedly. please guide me find cause of such behaviour , how fix this.

the output of rake:routes is:

bash-3.2$ rake routes     trackers        /trackers(.:format)                tracker#index         root        /                                  home#index        users post   /users(.:format)                   users#create    edit_user    /users/:id/edit(.:format)          users#edit         user    /users/:id(.:format)               users#show              put    /users/:id(.:format)               users#update              delete /users/:id(.:format)               users#destroy                     /auth/:provider/callback(.:format) sessions#create auth_failure        /auth/failure(.:format)            :controller#:action      signout        /signout(.:format)                 sessions#destroy                     /online/:id(.:format)              users#function 

please let me know if need more information.

your app doesn't have route /app/update_progress. 1 of below calling in app:

  1. javascript code in app (do use this bootstrap progressbar chance?)

    to test whether source of problem - open chrome developer tools , go network panel. open application localhost:3000. if see consistent calls in network tab localhost:3000/app/update_progress, means application firing these requests javascript. need search codebase find out javascript code is. may inside jquery extension have downloaded too. can create breakpoint in javascript whenever ajax request made /app/update_progress.

  2. a chrome/firefox extension

    to rule out, open chrome/firefox in incognito mode (which disables extensions), , open application. if still see hits /app/update_progress not extension causing problems.

  3. some external gem you're using

    if above 2 don't materialize, post gemfile.


Comments

Popular posts from this blog

SPSS keyboard combination alters encoding -

Add new record to the table by click on the button in Microsoft Access -

CSS3 Transition to highlight new elements created in JQuery -