[symfony-users] Re: Routing rules where the parameter to be set is not exactly what should appear in the URL

2009-02-14 Thread Tom Boutell
Hi Bernhard, Thanks for responding. You suggested: test_index: url: /test param: { module: test, action: index } test_images: url: /test/images param: { module: test, action: index, type: image } With that first rule in place, I would get the following results: test/index?type=image

[symfony-users] Re: Routing rules where the parameter to be set is not exactly what should appear in the URL

2009-02-14 Thread Bernhard Schussek
Hi Tom, It may be a silly suggestion, but why don't you just add the /test rule? test_index: url: /test param: { module: test, action: index } test_images: url: /test/images param: { module: test, action: index, type: image } On Fri, Feb 13, 2009 at 7:47 PM, Tom Haskins-Vaughan wrote:

[symfony-users] Re: Routing rules where the parameter to be set is not exactly what should appear in the URL

2009-02-13 Thread Tom Haskins-Vaughan
I may be completely off track here, but does the requirements field not use regular expressions? If it does, is there not something you can do like this: requirements: { type: (image|video)s } Tom Boutell wrote: > I spent some time puzzling over these two routing rules today: > > > image