And voila!


On 22/05/07, Mark Holton <[EMAIL PROTECTED]> wrote:
> encodeURIComponent() works like a charm!
> (sorry for the thinking out loud, but sometimes it seems to help)
> cheers-
>
>
>
> On 5/21/07, Mark Holton <[EMAIL PROTECTED]> wrote:
> > Is this a better js function to use?:
> >
> >
> encodeURIComponent()http://xkr.us/articles/javascript/encode-compare/
> >
> >
> >
> >
> >
> > On 5/21/07, Mark Holton <[EMAIL PROTECTED] > wrote:
> > > escape("string") ?
> > >
> > > ...wondering if there is a built-in Prototype.js way
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 5/21/07, Mark Holton < [EMAIL PROTECTED]> wrote:
> > > > Hello,
> > > >
> > > > I'm getting errors when I pass a "?" or a "#" to my server side code.
> So for instance, let's say I'm saving a "name" and a "memo", and someone
> decides to include a "?" in the text of their memo.  It causes an error when
> sent to the server side code.  Is there a way, in Prototype, to make sure it
> passes the whole string and to not interpret pieces of the string passed in?
>  I am passing the string in as $('txtMemo').value, for example.
> > > >
> > > > (when it's a numeric value, and in other cases I pre-process the
> string on the server side to avoid SQL-injection, etc, but these two
> characters in particular, "?", or "#" are causing the error to occur).
> > > >
> > > > Many thanks for any heads up there.
> > > > cheers,
> > > > Mark
> > >
> > >
> >
> >
>
>
>  >
>


-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to