routing

I am looking to generate some CSS files dynamically in my Content folder. At the moment, this folder has an ignore route ( routes.IgnoreRoute("Content/{*wildcard}"); ) and, I'd like that to remain, as I don't need/want most of my content folders to go into the MVC request lifecycle. Example: routes.MapRoute( "DynamicCSS", "Content/Css/Dynamic/{guid}.css", new { controller = "Site", action = "GenerateCSS" }, new { guid = @"^([0-9a-fA-F]){8}([0-9a-fA-F]){4}([0-9a-fA-F]){4}([0-9a-fA-F]){4}([0-9a-fA-F]){12}$" } ); //If the file has already been generated, IIS should just return the file, saving a

I have an SQLITE Database's File which in one of the table columns there is some simple Regular Expressions. These Expressions are something like /foo(. ?) or /foo/bar/(.?) and so on... Well, when we try to match some text against a Regular Pattern, in PHP, we do: preg_match( $pattern, $target, $matches ) Replacing the variables with the content, obviously. What I would like to do is send ANY STRING as value of a WHERE Clause and, when searching the SQLITE Database's File, use each of the stored Regular Expressions to match a pattern in the given string. I think that using PHP's sqlite_create

I have very simple question. My site, based on ASP.NET MVC, can have many urls, but all of them should bring to the one controller. How to do that? I suppose I need some magic in Global.asax but I don't know how to create route that will redirect any url to the specific controller. For example I have url /about, /product/id etc. but all of them should be really bring to the content/show where the parts of url will be recognized and the decision what information to show will be make. It's some like CMS when you cannot define routes in advance. Is this information enough? Thanks This sounds like

I'm new to Laravel and it seems a great framework but i have a question when it comes to routing. I want to route all get requests to one controller action named PageController@view but when the prefix is admin i want it to route to Admin\AdminController@view. I have the following code: Route::get('/{slug?}', 'PageController@view'); Route::group(array('prefix' => 'admin', 'namespace' => 'Admin', 'before' => 'auth'), function() { Route::get('/', 'DashboardController@main'); }); But when i go to: /admin, Laravel treats it like a slug instead of a prefix. Is there somekind of except function for

I am using cakephp in one of my projects and my client wants the site URLs to end with .html and not the usual friendly urls. I was wondering if its possible in cakephp to do so through any of its routing techniques. Please help. That is well documented in the cookbook . UPDATE: http://book.cakephp.org/2.0/en/development/routing.html#file-extensions To handle different file extensions with your routes, you need one extra line in your routes config file: Router::parseExtensions('html', 'rss'); If you want to create a URL such as /page/title-of-page.html you would create your route as

I am new to Laravel framework. I am using 4.2 my question is i had a pagination functionality in a manageemployee page, I have created a route for manageemployee page. Route::get('/usercp/manageemployee',array('uses' =>'ManageEmployeeController@getManageCompanyEmployee','as' =>'getManageCompanyEmployee')); In this page i have pagination , if user was in third page, he want to delete one record. now the page looks like /usercp/manageemployee?page=3 After deleting a particular record in that page i need to redirect user to the same page. My Redirect code as follows return Redirect::route(

I know that if you think you found a bug in the .NET framework you are most likely wrong, but that's why I'm writing this question, so please hear me out. I am fairly certain that there is a difference between the routes in .NET 3.5 and .NET 4.0 when it comes to optional parameters. Specifically if you have more than one optional parameter in your route. I have not been able to find this breaking change noted in any release notes of either .NET 4.0 or MVC 3 so thats why I call it a bug. EDIT: This bug only manifests itself when you try to build a route url using code like the url or html

I'm implementing a site login that takes in an email/password combo, retrieves an API token, and returns it to the user to get stored (encrypted) in localStorage. Currently, on successful POSTing to /login , the app redirects the user to the index page, with the token attached as a query, like so (as suggested here ): login.post('/', function(req, res) { ...checking password... Auth.getToken(user, function(err, token) { res.redirect('/?token=' + token); }); }); This works fine, but I'd prefer to keep my URLs as clean as possible and set the token as a header instead: login.post('/', function

Test Case https://codesandbox.io/s/rr00y9w2wm Steps to reproduce Click on Topics Click on Rendering with React OR Go to https://rr00y9w2wm.codesandbox.io/topics/rendering Expected Behavior match.params.topicId should be identical from both the parent Topics component should be the same as match.params.topicId when accessed within the Topic component Actual Behavior match.params.topicId when accessed within the Topic component is undefined match.params.topicId when accessed within the Topics component is rendering I understand from this closed issue that this is not necessarily a bug. This