urlencode() each parameter, separated by slashes. It'll get there.

Eric


On 12/30/06, Alexis Konstantinou <[EMAIL PROTECTED]> wrote:

Thanks for the reply,

I know this works if storing params in $_GET. My question was: what if I
want to use the SLASH format for passing URL's instead of the traditional
method

i.e.
I want something like this:
http://www.somthing.com/controller/view/param1/param2/param3
=> controller will contain a function view with parameters param1,param2 and
param3


instead of using something like this:
http://www.somthing.com/controller/view?p1=param1&p2=param2&p3=param3





On 29/12/06, Nimrod A. Abing <[EMAIL PROTECTED]> wrote:
>
>
> On 12/29/06, @leX <[EMAIL PROTECTED]> wrote:
> >
> > I'm using the SLASH format for passing params to controller from a URL
> > so that users can modify the url
> >
> > i.e. http://www.somthing.com/controller/param1/param2/param3
> >
> > last param (i.e. param3) is a string which may contain characters such
>
> > as question marks '?' or even forward slashes '/'. As you probably
> > already know, these characters are reserved chars for URL's with some
> > special meaning.
> >
> > Is there a function in cakephp for coding these string to allow me to
> > pass strings via the url (e.g. hash the string or something like
> that).
>
> http://php.net/urlencode
> http://php.net/urldecode
>
> Or
>
> http://php.net/base64_encode
> http://php.net/base64_decode
>
> When using urlencode() to encode the parameter, there is no need for
> you to urldecode() the parameter when extracting it from $_GET.
> --
> _nimrod_a_abing_
>
> [?] http://abing.gotdns.com
>
>
> Alexis Konstantinou
>
> > >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to