ID: 7615 User Update by: [EMAIL PROTECTED] Old-Status: Feedback Status: Open Bug Type: Other web server Description: Session management in thttpd / proxy problem James, This works OK: thttpd <-> Firewall w/NAT <-> Internet <-> ISP <-> Client This doesn't: thttpt <-> Firewall <-> Internet <-> ISP <-> Proxy <-> Client Seems that either thttpd/php does not deliver the 'proxy-no-cache' pragma or that the proxy filters out the 'no-cache' pragma on the way to the client browser. Regards, Ben Previous Comments: --------------------------------------------------------------------------- [2001-05-01 08:58:54] [EMAIL PROTECTED] Can you please try this without the firewall inbetween you and the webserver and see if the firewall delay is causing the problem or if it is definatly a PHP-Thttpd problem. - James --------------------------------------------------------------------------- [2000-12-26 04:51:27] [EMAIL PROTECTED] I think the initial post pretty much sums it up. I haven't got any sample page/app ready with authentication, cookies _and_ a firewall in between. But Dragonflymail/Squirrelmail is pretty easy to install and should yield the desired behaviour. Don't you have kinda regression test suites ready at php's? Now this would be a very useful addition. Regards, Ben --------------------------------------------------------------------------- [2000-12-22 20:02:56] [EMAIL PROTECTED] Do I understand you correctly that thttpd/PHP does not read the POST data completely? If that is the case, PHP might not be able to get the correct POST data. Can you provide an example for this situation (i.e. a form which gets submitted to a server which displays the variables it received)? --------------------------------------------------------------------------- [2000-11-03 05:11:26] [EMAIL PROTECTED] I installed thttpd-2.20b with PHP 4.0.3pl1 with --with-trans-sid, --with-imap --with-sockets --with-thttpd. I have Squirrelmail and Dragonflymail installed to check them out. Both worked. When trying to access them via a company's firewall, login was not possible, neither via trans-sid nor cookies. 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. It simply does not seem to wait until the client had answered *all* questions. It seems that the client has no time to transmit session IDs *and* POSTing the login information. I've read somewhere that someone had as similar problem with apache which he solved by adding a delay in the session-buildup routine. I don't know if this is a thttpd problem or php-in-thttpd problem. Other pages (that had nothing to do with session stuff) just work fine. For the time being, I leave apache installed although its footprint is way bigger than thttpd's... Regards, Ben --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=7615 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
