ruby - how to ensure that a user can not redirect to another element in the child engine from within the parent engine -


i have engines mounted inside engines engine made congregation of multiple child elements various engines. engine mounted in main app. routes follows:

rails.application.routes.draw    namespace :parent_engine, :path  => "/foo"     match "/", :to=>"parent_engine#index"      resources :parent_engine , :only=>[:show]       mount engine1::engine => '/engine1'       mount engine2::engine => '/engine2'     end   end end

now when wish see element "engine1" have url 

/parent_engine/:id/engine1/object_type/:id

the trouble facing need stop user being able access object of engine1 explicitly updating url in browser. eg:

from:

/parent_engine/1/engine1/object_type/1

to:

/parent_engine/2/engine1/object_type/2

also can not put check in mounted engines these mounted seperately in container app well. dont want user able able redirect object instance when inside context of parent engine.

thanks , regards in advance.

i'm not sure try do, suspect may able use route constraints:

rails.application.routes.draw    namespace :parent_engine, :path  => "/foo"     match "/", :to=>"parent_engine#index"      resources :parent_engine , :only=>[:show]       mount engine1::engine => '/engine1', :constraints => engine1contraint.new       mount engine2::engine => '/engine2'     end   end end

then can define config/initializers/engine1_contraints.rb with

class engine1contraint   def matches?(request)     request.path != 'something' || request.env['warden'].user == 'admin'   end end

or whatever rules need adjust there, mother engine control on child engines.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more