Child pages
  • Complementary mod-rewrite url parameter transformation scheme
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/2e6ea47ce3fd5674#

I propose to add ability (on/off via configuration variable) to transform all url parameters (except of "env" of course) in form "/parameter_name/parameter_value". For example:

before: http://www.site.com/path/to/template.html?size=large&page=14
after: http://www.site.com/path/to/template/size/large/page/14.html

Don't know, how useful this could be though.

4 Comments

  1. Idea is very interesting and I believe has potential, but what happens
    to more complex URL build for "Mod-rewrite Listeners"?

    How these all will mix up? can you provide more samples?

    To see what I mean look at this:

    http://www.vic.gov.au/calendar/2010/01.html?filter_type=category&filter_value=8934

    This is "Custom Mod-rewrite Listener" not from 5.0.1, but works very
    similarly and as you can see there are variables... Can you adapt this
    to work as you proposing?

    Thanks!

    DA.

  2. Unfortunately my proposed approach has no AI to detect what to parse and
    what's not, no I guess it could be enabled globally, especially for case
    when total url part count isn't odd, e.g. 7.

    This idea, however could be implemented in any of user-made rewrite
    listeners, when it need it.

  3. Yes, that's what I thought... but it's ok for now.

    I say we wait! experiment and see how this is useful and new Mod-
    Rewrite Listeners work all together since it's kind of new approach
    for everyone.

    Later we can come back to this topic and put more time into this or
    some of In-Portal users might raise this question earlier.

    DA.

  4. This idea proposed by me originally violates URL building logic, where facet filters must be passed in QueryString and not in main URL part (before .html).