Hi Scott, Just bringing to the attention for the list a limitation that I just found out and is undocumented
there is no limit set by rfc 2109 http://www.w3.org/Protocols/rfc2109/rfc2109 and in searching around on Google there are article about cookies 2500 chars. So, I will have to create Cookie Crumbs Cookie Crumb = Data Larger than 128 char split into multiple cookies This has been an interesting ride, I need some milk now Ben Johansen - http://www.pcforge.com -Authorized WiTango Reseller http://www.pcforge.com/WitangoGoodies.htm -Authorized Alt-N Reseller http://www.pcforge.com/AltN.htm -----Original Message----- From: Scott Cadillac [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 9:17 PM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: cookies Hi Atrix and Ben, Cookie data is very limited in size. This is a limitation of the HTTP spec - not Witango. Cookie data can only be a single scalar value (text) and probably limited to the kinds of characters you can use. Carriage-returns are a no-no for sure, because they mark the end of the HTTP Header line and the beginning of another property - so can cause corruption of the Header, if not used in the right place (such as a cookie value). Hope this adds to the taste..... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- -----Original Message----- From: Atrix Wolfe [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 10:01 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: cookies Funny you should mention that Ben! i was just playin around seein if i could store a resultset in a cookie and it wouldnt take. I guess you could always make code to split what you wanted to store in 128 character segments though hehe (: I dont know why 128 chars but im betting it has something to do that 1 byte has 256 values, and half of that is 128 :P You couldnt do that cookie thing to bring down the server from the browser side could ya? interesting stuff these cookies! (: ----- Original Message ----- From: Ben Johansen To: [EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 8:44 PM Subject: RE: Witango-Talk: cookies Thanks Scott, - forgot about session cookies are store in a virtual cookie jar not in the actual cookie jar Thanks Witango Man -for the GUI Cookie (must be chocolate chip on a hot summer day ;-) a big plus to using the Assign action is nice and easy expire date select One gotcha, That I ran into very abruptly recently there is a limit of a length of 128 characters to the cookie data. if you go over the limit it there is varying results on like Witango 4 (T2k) it will shot down the server service like... <@ASSIGN Witango_UserReference VALUE="abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdea bcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeab cdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabc deabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcd eabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde" SCOPE=cookie> you are taking a trip to the server to restart the service But... on Witango 5 the latest build 062 it just truncates it to 128 characters Not sure why the limit of 128 chars??? Ben Johansen - http://www.pcforge.com -Authorized WiTango Reseller http://www.pcforge.com/WitangoGoodies.htm -Authorized Alt-N Reseller http://www.pcforge.com/AltN.htm -----Original Message----- From: witango man [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 7:56 PM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: cookies Just to add to Ben's post - if you using an Assign action - set the scope to cookie - right click and select properties - in there you can set the other cookie attributes as Ben described (Bens method is just as good but if you want to use a GUI instead....) Ben Johansen <[EMAIL PROTECTED]> wrote: I have been through a crash course on cookies :-b they are interesting critters. ok first let me explain about the Cookie Jar. (using windows in these examples) Under your Windows folder or Document Settings folder depending on version of OS there is a folder usually called cookies. these files are .TXT standard text files and you will notice the they have usually your {network [EMAIL PROTECTED] domain}.txt these are the Cookie Jar files. You have no control over the cookie this is a handled by the browser in communication with server you are connected to the drops the cookie on you. the Cookie Jar holds Cookies. Cookies are like ARGs in that there contain Name=Value pair with a few extra attributes A Cookie Name = Cookie Name (required) Value = Cookie Data (required) Path = the path usually "/" for root Expires = GMT Date on how long the cookie will stay in the Jar Secure = true or false true means the cookie can only be read by an HTTPS secure connection Have you ever wondered what those extra attributes on the @ASSIGN where for, well now you know <@ASSIGN NAME=name VALUE=value [SCOPE=myscope] [EXPIRES=timestamp] [PATH=path] [DOMAIN=domain] [SECURE=true|false]> it is just that easy to drop a cookie just set the scope as COOKIE <@ASSIGN NAME="HELLO" VALUE="THERE" SCOPE="COOKIE"> Now this code will place an entry into the COOKIE JAR as HELLO=THERE; Without specifying the EXPIRES attribute this is a SESSION cookie (kinda of like Local/Request Scope) when you leave the domain that dropped the cookie the HELLO=THERE; will be deleted from the Cookie Jar. to set the EXPIRES so the the cookies stays there in the jar use code like --- <@ASSIGN NAME="expsec" VALUE="<@CALC EXPR='((60 * 60) * 24)'>" SCOPE="local"> <@ASSIGN NAME="expirey" VALUE='<@TOGMT TS="<@SECSTOTS SECS='<@CALC EXPR="<@TSTOSECS TS=<@CURRENTTIMESTAMP>>+@@local$expsec">'>">' SCOPE="local"> <@ASSIGN NAME="expirey" VALUE='<@FORMAT STR="@@local$expirey" FORMAT="datetime:http" INFORMAT="datetime:<@VAR NAME='timestampFormat'>">' SCOPE="local"> @@local$expirey --- Like... <@ASSIGN NAME="HELLO" VALUE="THERE" SCOPE="COOKIE" EXPIRES="@@local$expirey"> Now, the cookie will stay in the Jar without molding ;-) Ok, you say now I have a Cookie in a Jar on there computer, how do I Eat it all you have to do is reference the Name of the Cookie in the COOKIE scope <@VAR NAME="HELLO" SCOPE="COOKIE"> or @@cookie$HELLO That's it. You are now Eating and Tossing Cookies ;-) There is some more but this will get you started Ben Johansen - http://www.pcforge.com -Authorized WiTango Reseller http://www.pcforge.com/WitangoGoodies.htm -Authorized Alt-N Reseller http://www.pcforge.com/AltN.htm -----Original Message----- From: Atrix Wolfe [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 6:22 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: cookies Hey Ben, you said cookies could offload variable storage. I dont know anything about cookies, is that data stored in files on the user's computer or is it more like post args or something else? It sounds really cool, is it easy to do in witango? ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
