Yes, it really is an issue, as several sites that I'm pulling the data from
require login, and they don't recognize the URLEncoded session cookies sent
by CF.
Russ
_____
From: Dave Carabetta [mailto:[EMAIL PROTECTED]
Sent: Friday, September 03, 2004 11:31 AM
To: CF-Talk
Subject: Re: CFHTTP Alternatives
On Fri, 3 Sep 2004 11:18:05 -0400, Russ <[EMAIL PROTECTED]> wrote:
> I did read the docs. The docs state:
>
> encoded
>
> Optional
>
> Yes
>
> Applies to FormField and CGI types; ignored for all other types. Specifies
> whether to URLEncode the form field or header.
>
> I am using it on a cookie type.
>
Ah, you never mentioned you were using it on cookies. However, is this
really an issue for you? We have a PDF engine written in Python that
runs on Linux that does a callback to a CF page, and the cookies
transfer fine for us (and if they weren't, our stuff would break
because it relies on the CFID/CFTOKEN values in the user's cookie for
client variable stuff).
Regards,
Dave.
_____
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
[Donations and Support]
- CFHTTP Alternatives Russ
- Re: CFHTTP Alternatives Dave Carabetta
- RE: CFHTTP Alternatives Russ
- Re: CFHTTP Alternatives Dave Carabetta
- Re: CFHTTP Alternatives Jochem van Dieten
- Re: CFHTTP Alternatives Dave Carabetta
- Re: CFHTTP Alternatives Andrew Grosset