On 8/30/07, warrell harries <[EMAIL PROTECTED]> wrote:
> Can you use the {request-param:lon1} input module?
>
> e.g.
> <redirect-touri="cocoon:/stops?lat1={request-param:lat1}&lon1={request-param:lon1}&lat2={request-param:lat2}&lon2={request-param:lon2}"/>
That won't work because in the original (alias) URL, the parameters
are not named by anything other than position:
<match pattern="stops/(*,*),(*,*)">
It might be more clear to expand on the other example. I'd like to be
able to do this:
<match pattern="stops/*/schedule">
<redirect-to uri="cocoon:/schedules?stopNumber={1}"/>
</match>
Making it even more complicated is something I forgot about: the URLs
have optional parameters, too, that need to be passed on in the
underlying request. Example:
stops/10064/schedule?time=2007-09-03
|
-> schedules?stopNumber=10064&time=2007-09-03
I could easily do that if CInclude worked the way I expect. Is there a
way to get the parameters of a cocoon: protocol URI to go through?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
