Hi all, I have discovered an issue with the way web2py treats the "cookies" header. Specifically, when the header grows bigger than a certain size, web2py doesn't retrieve all the required cookies for the domain in question.
In my case, the application is running on an intranet for a rather big company. This means that many cookies are potentially available to an application (those that are stored at the domain level) meaning that the length of the overall cookies header grows. If I iterate over all the headers in Java (JSP) I get a complete set. If I then redirect to a web2py application, I only get the first x headers (where x is dependant of the previous cookie's lengths). The * request.env.http_cookie* variable is complete however. Whilst I've managed to code around this issue (by writing my own cookie retrieval function that parses request.env.http_cookie) there is a problem with the inbuilt session management code as it uses the underlying (broken) cookie code to store the session ID. I haven't had a chance to look at the source code for cookie management in web2py but wanted to check whether anyone else had experienced this issue? Regards, Dominic. --
