Lukas Gebauer wrote: >> I don't have a clear idea how the cookies should be parsed, but I see >> that THTTPSend.ParseCookies gets just the first pair from a cookie. >> >> E.g. a web site is setting two cookies: >> Set-Cookie: id=123; id2=abc >> Set-Cookie: time=1234; id3=65erty >> > > One Set-Cookie header can contain only one cookie by definition! If > soe server sending to you more then one cookie on one line, then this > server is broken. > > It is because line part after semicolon are not next cookies, but > attributes of cookie. For example header: > > Set-Cookie: RMID=732423sdfs73242; expires=Fri, 31-Dec-2010 23:59:59 > GMT; path=/; domain=.example.net > > .. this is not set of cookies, it is ONE cookie called RMID. Value > (what will be sended back to server) of this cookie is > 732423sdfs73242. All next informations in headr are just attributes > of RMID cookie usefull for some cookie manager for know if cookie can > pass policy checks and for know when cookie will be expired. It is > not next cookie with name 'expires'! > > Synapse not have any cookie manager. So, only name and value are > parsed and stored. > Thank you very much for the explanation.
regards Boban Spasic ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
