Skip to main content
Inspiring
July 13, 2006
Question

encoding the "&" when using urlsessionformat()

  • July 13, 2006
  • 1 reply
  • 336 views

The function doesn't encode the "&" when appending the cftoken and cfid
values to the query string, thus the code it renders may not validate.
Is there a way I can tweak it or a fix or a udf that replicates it correctly
and no slower, rather than having to use two functions - one for the
urlsessionfomat() and one to replace the "&" 's it generates with their
encoded equivalent?

--
Cheers,
Lossed
__when the only tool you have is a hammer, everything looks like a nail __


    This topic has been closed for replies.

    1 reply

    Inspiring
    July 15, 2006
    Bumping in the hope someone can help.

    It does peeve me a tad the urlsessionformat() function isn't returning a
    query string that validates.

    Is it something I should file a bug report about? If so, where might I check
    if this has already been noted and where do I file such a report?

    And, if anyone has any suggestions (apart from nesting it in yet another
    function to replace the ampersands with their encoded equivalents), I'm all
    ears :)

    Tks.

    "Lossed" <blankemail@hotmail.com> wrote in message
    news:e94mq2$426$1@forums.macromedia.com...
    >
    > The function doesn't encode the "&" when appending the cftoken and cfid
    > values to the query string, thus the code it renders may not validate.
    > Is there a way I can tweak it or a fix or a udf that replicates it
    > correctly and no slower, rather than having to use two functions - one for
    > the urlsessionfomat() and one to replace the "&" 's it generates with
    > their encoded equivalent?
    >
    > --
    > Cheers,
    > Lossed
    > __when the only tool you have is a hammer, everything looks like a nail __
    >


    October 21, 2006
    Same predicament here Lossed. Did you find any solution that you wouls like to share?
    Thank you.
    October 21, 2006
    How about HTMLEditFormat (URLSessionFormat (...))?