routing

问题 First, this is not MVC, WebForms only.. I'm using routing to keep my site backwards compatible for our clients, while make my project organized. I'm also thinking of moving our encrypted query string to a more friendly url. How this works is our clients have to bookmark a huge encrypted url to prevent them from guessing our other clients by changing an id around. But instead of having this huge url, wanted to add a route like LoginClientName.aspx for each client and have the encrypted query

问题 I have routes like: /, /login, /register, etc that work fine in dev environment. At first i got 404 error when tried to access my site through app.php instead of app_dev.php Then i followed this advice and cleaned up my cache. But now i'm getting a blank screen trying to access any of the registered routes like app.php/ or app.php/login. I found this message in prod.log: [2012-02-24 11:27:05] request.ERROR: Symfony\Component\HttpKernel\Exception\NotFoundHttpException: No route found for "GET

问题 Is there a specific pattern that developers generally follow? I never really gave it much thought before in my web applications, but the ASP.NET MVC routing engine pretty much forces you to at least take it into consideration. So far I've liked the controller/action/index structure (e.g. Products/Edit/1), but I'm struggling with more complex urls. For instance, let's say you have a page that lists all the products a user has in their account. How would you do it? Off the top of my head I can

问题 I am using a route like this match "/v1/:method" => "v1#index" My intention here is capture the name of the api method and then send the request to that method inside the controller. def index self.send params[:method], params end I figured this would send the other parameters as an argument to the method, but it didn't work. So my question is how can I pass the non-method parameters in a query string? 回答1: #query_parameters does exactly what you want: request.query_parameters It's also the

问题 I have created some custom content types which include the route part so my content managers can edit the slugs for the items. I am having no luck configuring a route that will enable a controller of my own to serve requests for these items. The route for paths to the ItemController in the core Routable module has a priority of 10. I have tried making a route that utilises an IRouteConstraint, similar to how the Blog module achieves what I want to do, with a lower priority but still no luck.

问题 I have created some custom content types which include the route part so my content managers can edit the slugs for the items. I am having no luck configuring a route that will enable a controller of my own to serve requests for these items. The route for paths to the ItemController in the core Routable module has a priority of 10. I have tried making a route that utilises an IRouteConstraint, similar to how the Blog module achieves what I want to do, with a lower priority but still no luck.

问题 Where to test routes in ruby on rails? unit tests? functional tests? integration tests? Addition: To be exact, where to apply assertions described on guides and on api? 回答1: Routes should be done as part of integration tests. Integration tests are where you test the important work flows of your application - more specifically whether a URL is defined or not seems to be an important workflow. Your integration test would look like any normal integration test: # /tests/integration/routes_test.rb

问题 I'm working on Symfony 2.3 and I declared a new route and new controller , but when I call this controller from the browser I get this error: The controller for URI "/user/1" is not callable. in /dev.mydomain.org/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Controller/ControllerResolver.php at line 82 This is my simple route configuration: user_homepage: pattern: /user defaults: { _controller: UserBundle:Default:index } user_show: pattern: /user/{id} defaults: { _controller:

问题 I understand that when sending ip messages around, each hop in the network path between be and my packet's destination will check if the next hop's MTU is bigger than the size of the packet I sent. If so, the packet will be fragmented and the two packets will be separately sent to the next hop, only to be reassembled at destination (or, in some cases, at the first NAT router encountered). As far as I understand, this thing can be pretty bad, but I don't really understand why. I understand

问题 I understand that when sending ip messages around, each hop in the network path between be and my packet's destination will check if the next hop's MTU is bigger than the size of the packet I sent. If so, the packet will be fragmented and the two packets will be separately sent to the next hop, only to be reassembled at destination (or, in some cases, at the first NAT router encountered). As far as I understand, this thing can be pretty bad, but I don't really understand why. I understand