routing

My Angular 4 web-app routing works fine in my dev environment, and the menu redirects work fine on the live version. However, the dev version redirects to different pages by typing in the address field of the browser, but the live version doesn't. Is this an Angular problem? Or do I need to manage my redirects with my ISP? My app.router.ts code is as follows: import { ModuleWithProviders } from '@angular/core'; import { Routes, RouterModule } from '@angular/router'; import { HomeComponent } from './home/home.component'; import { ArtComponent } from './art/art.component'; import {

I'm in the need for a routing library to handle my paths for a client side js app. I'm currently using backbone.js, which while great, is not fully featured enough. I'm looking for a dedicated pathing library that I can replace backbone with (only in terms of pathing, still want to use that for MVC), something with a lot of features. Thanks There are a number of interesting routing libraries at http://www.microjs.com/#spa Backbone, and Crossroads (and its accompanying library, Hasher) are both listed there, but you should also check out Director (independent module from the Flatiron framework)

Is that possible with symfony2 to define multiple url patterns for a single Controller Action using regular expressions, so we don't have to define several rules ? Thanks in advance Do you mean placeholders with requirements? blog: pattern: /blog/{page} defaults: { _controller: AcmeBlogBundle:Blog:index, page: 1 } requirements: page: \d+ Here you have multiple routes defined by a placeholder, validated by regular expressions going to the same controller action. Edit: Each part of the url can be a placeholder. blog: pattern: /{type}/{page} defaults: { _controller: AcmeBlogBundle:Blog:index,

I am starting now with Camel. I have seen the http4 component for http clients and the jetty component for http servers. I have seen several examples that use one or the other. I would like to know if it is possible to combine them together. Example from("jetty:http://0.0.0.0:8080/myapp/myservice") .to("http4://www.google.com"); This would make camel a simple http based router/proxy. Web browsers would hit the camel URL and instead get google. (Google is just an example, I have a real POST based service that I want to use) Is this route possible? Should I research Camel or do I need a

I have a request spec in a Rails engine. The view that is rendered calls a route and passes in a hash, i.e. projects_path(:scope => "user") . A route like this will eventually call url_for , but url_for is defined in many places. When running the application or running a request spec in the main app (root level), the call chain ends up at ActionView::RoutingUrlFor#url_for ; when running a spec in the engine, however, the call chain ends up at ActionView::Helpers::UrlHelper#url_for . In Rails 4, the url_for method defined in UrlHelper no longer accepts hash arguments, so I'm left with this