|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2001-05-07 12:49 UTC] derick@php.net
[2001-10-16 01:40 UTC] ssb@php.net
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sat Nov 01 13:00:01 2025 UTC |
Short script: <? mysql_connect("10.0.0.244", "user", "passwd");?> Really any socket connection code. Configure Command: './configure' '--with-apxs=/usr/sbin/apxs' '--with-mysql=/usr' '--with-mcrypt=../mcrypt-2.2.6' '--with-mhash=../mhash-0.8.4' '--with-ldap' '--with-fdftk' '--with-pdflib' '--with-zlib' '--with-gd' '--with-pspell' '--with-oci8' '--with-java=/opt/IBMJava2-13' '--enable-sigchild' Pretty much the default php.ini. We noticed this occurring once we put the machine inside a DMZ. If PHP tries to connect to an address that the DMZ isn't allowing, the DMZ throws the packets away and PHP sits there waiting for a response. This only happens when session_start() is called in the page. If session_start() is commented out, the normal PHP warnings appear telling me of mysql or ldap not being able to connect.