Hello, The error that you see with cookies is indeed not necessarily a problem. Wt can interpret its own cookies, but our parser is a little pedantic about cookie syntax, and does not like all cookies from all other sites (there are some real junk cookies around, too). This can be a problem if you enabled session tracking using cookies, as the parser will stop at the parse error. We will work on this in the future. The cookie causing the problem is not Wt cookie but a cookie from another website/application running on your server (localhost?).
But, using cookies for session tracking is not recommended and disabled by default: - a user can only use a single session per web browser, which is not very natural - there are in general security concerns related to using cookies (such as CSRF, but Wt protects against this by not relying on cookies for session tracking). Wt uses cookies only in the event that the user presses the reload button. With respect to konquerer not being very functional: that is a known issue which is on our todo list. Best regards, Wim Dumon. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
