![]() I've read somewhere that someone had as similar problem with apache which he solved by adding a delay in the session-buildup routine. It seems that the client has no time to transmit session IDs *and* POSTing the login information. It simply does not seem to wait until the client had answered *all* questions. I ran a network trace against both thttpd and apache (on which the very same box with the very same apps work) and saw that thttpd is very quick (as not to say impatient) at session build-up. When trying to access them via a company's firewall, login was not possible, neither via trans-sid nor cookies. I have Squirrelmail and Dragonflymail installed to check them out. Tictactux at surfeu dot ch I installed thttpd-2.20b with PHP 4.0.3pl1 with -with-trans-sid, -with-imap -with-sockets -with-thttpd.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |