php-windows Digest 14 Aug 2004 06:37:52 -0000 Issue 2359
Topics (messages 24409 through 24415):
PHP 5.0.1 is out, so is WAMP5 1.2 for Windows !
24409 by: Romain Bourdon
Re: connection: close header
24410 by: Gryffyn, Trevor
24412 by: d c
24413 by: Justin Patrin
24414 by: Gryffyn, Trevor
PHP 5.0.1 Released!
24411 by: Andi Gutmans
Error After Installing Mambo
24415 by: Q.Reyes
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
--- Begin Message ---
The new version of WAMP5 is now online. WAMP5 now includes PHP 5.0.1, the
PECL extensions, sqlitemanager 0.9.8. Many other new features have been
added, to know them see the changelog on the wampserver web site :
http://www.en.wampserver.com
Of course you can directly upgrade from version 1.0 or 1.1 (except if you
have installed the Apache 2 add-on, in that case, save all your data,
uninstall and reinstall).
Have fun
Romain
--- End Message ---
--- Begin Message ---
Yeah, I understand that bit. Persistent connections to the web server
make sense to me. What doesn't make sense is why you'd require a
persisent connection for something to work. The workstation might be
persistently connected to the web server, but a PHP, ASP or HTML page is
going to send it's data, then stop. Then you send another request to
the web server and it sends more data to you. Then you make another
request and it sends more data. Whether you're persistent or not
shouldn't make something break as far as I know. It might make things a
little slower because of having to renegotiate the connection, but since
HTTP is connectionless by nature, the data it sends doesn't require
persistent connection.
That's what sessions are for, isn't it?
Not trying to be antagonistic, I just don't understand why a persistent
connection is required for this to work. Maybe Dave is asking the wrong
question.
Ok, working with Dave's response to this where he says that he doesn't
have the option of changing the client, let's focus on the PHP page that
the application is accessing.
Dave, describe "Not working correctly". What is the nature of the data
the application sends to the PHP and ASP pages, why does it need a
persistent connection (again, maybe this isn't the right question to
solve this problem) and what's the PHP page doing that the ASP doesn't.
Is it not retrieving all the data or something?
A little more detail might help solve this one.
-TG
> -----Original Message-----
> From: Justin Patrin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 12, 2004 5:45 PM
> To: Gryffyn, Trevor
> Cc: [EMAIL PROTECTED]; d c
> Subject: Re: [PHP-WIN] connection: close header
>
>
> On Thu, 12 Aug 2004 15:38:02 -0400, Gryffyn, Trevor
> <[EMAIL PROTECTED]> wrote:
> > Just tossing out my 2cents.. Maybe there's a way or a
> reason, but HTTP
> > connections are, by their nature, connectionless. They
> send the data
> > and close the connection. I'm not sure why you'd want to keep a
> > persistant connection to a specific page.
> >
> > There are "Keep Alive" codes you can send that maintain a
> connection to
> > the web server so you don't have to go through all the
> handshaking and
> > stuff again (ok, I'm not using exact terms here, forgive me.. My
> > networking is a bit rusty) but that doesn't keep you connected to a
> > single PHP or HTML or ASP page, just the server.
> >
> > Sounds like everything's behaving just as it was designed
> to and you're
> > trying to do something really odd. But maybe I'm just not
> getting what
> > you're trying to do or something.
> >
>
> Actually, this is something that's supported by the HTTP protocol. You
> use the same TCP connection (stream) for multiple requests to the
> webserver. It is a bit strange, but it's supported.
>
> Sounds like the OPs webserver isn't allowing the persistent
> connections to go through. Maybe Apache needs to be configured
> differently. Or PHP might be doing it. Or maybe the client application
> should be rewritten to not use persistent HTTP connections. ;-)
>
> > Just what popped into my head when I read this.
> >
> > -TG
> >
> >
> >
> > > -----Original Message-----
> > > From: d c [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, August 12, 2004 2:51 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: [PHP-WIN] connection: close header
> > >
> > >
> > > Hello,
> > >
> > > I am using php 4.3.4 on windows 2000 with iis 5 and isapi. We
> > > recently switched from asp to php. There is an application
> > > that we have that hits one of the pages to send some info,
> > > and it uses persistant connections. The php page was not
> > > working correctly, and a trace using ethereal showed that the
> > > difference was the "Connection: close" header being sent with
> > > the php page, while the "Connection" header was not present
> > > in the asp page's response. I tried using the latest version
> > > of php, and the header is still being sent.
> > >
> > > Is there a way to get iis to not close the connection with php?
> > >
> > > Thanks,
> > > Dave
> > >
>
> --
> DB_DataObject_FormBuilder - The database at your fingertips
> http://pear.php.net/package/DB_DataObject_FormBuilder
>
> paperCrane --Justin Patrin--
>
--- End Message ---
--- Begin Message ---
The page is for uploading files. The client posts some info about the file, and also
the file itself. The file is actually sent in chunks. The client is hitting the page
multiple times until all of the chunks for the file are uploaded. All of the data is
being sent the the php page, and the first chunk/file info are stored in the db. Since
the client is trying to re-use the connection, the other chunks are not getting sent.
It is instead timing-out. Simulating the client in a web browser will upload all of
the chunks, hitting the page multiple times. I don't know why the client was written
to try to use persistant connections. It doesn't make sense to me to do it that way,
but that's the way it is.
With the client, it works on Apache on Windows, but not with IIS. The only difference
between Apache and IIS is the "Connection: close" header present from IIS. The only
difference with the asp page and the php page on IIS is the "Connection: close" header
also.
"Gryffyn, Trevor" <[EMAIL PROTECTED]> wrote:
Yeah, I understand that bit. Persistent connections to the web server
make sense to me. What doesn't make sense is why you'd require a
persisent connection for something to work. The workstation might be
persistently connected to the web server, but a PHP, ASP or HTML page is
going to send it's data, then stop. Then you send another request to
the web server and it sends more data to you. Then you make another
request and it sends more data. Whether you're persistent or not
shouldn't make something break as far as I know. It might make things a
little slower because of having to renegotiate the connection, but since
HTTP is connectionless by nature, the data it sends doesn't require
persistent connection.
That's what sessions are for, isn't it?
Not trying to be antagonistic, I just don't understand why a persistent
connection is required for this to work. Maybe Dave is asking the wrong
question.
Ok, working with Dave's response to this where he says that he doesn't
have the option of changing the client, let's focus on the PHP page that
the application is accessing.
Dave, describe "Not working correctly". What is the nature of the data
the application sends to the PHP and ASP pages, why does it need a
persistent connection (again, maybe this isn't the right question to
solve this problem) and what's the PHP page doing that the ASP doesn't.
Is it not retrieving all the data or something?
A little more detail might help solve this one.
-TG
> -----Original Message-----
> From: Justin Patrin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 12, 2004 5:45 PM
> To: Gryffyn, Trevor
> Cc: [EMAIL PROTECTED]; d c
> Subject: Re: [PHP-WIN] connection: close header
>
>
> On Thu, 12 Aug 2004 15:38:02 -0400, Gryffyn, Trevor
> wrote:
> > Just tossing out my 2cents.. Maybe there's a way or a
> reason, but HTTP
> > connections are, by their nature, connectionless. They
> send the data
> > and close the connection. I'm not sure why you'd want to keep a
> > persistant connection to a specific page.
> >
> > There are "Keep Alive" codes you can send that maintain a
> connection to
> > the web server so you don't have to go through all the
> handshaking and
> > stuff again (ok, I'm not using exact terms here, forgive me.. My
> > networking is a bit rusty) but that doesn't keep you connected to a
> > single PHP or HTML or ASP page, just the server.
> >
> > Sounds like everything's behaving just as it was designed
> to and you're
> > trying to do something really odd. But maybe I'm just not
> getting what
> > you're trying to do or something.
> >
>
> Actually, this is something that's supported by the HTTP protocol. You
> use the same TCP connection (stream) for multiple requests to the
> webserver. It is a bit strange, but it's supported.
>
> Sounds like the OPs webserver isn't allowing the persistent
> connections to go through. Maybe Apache needs to be configured
> differently. Or PHP might be doing it. Or maybe the client application
> should be rewritten to not use persistent HTTP connections. ;-)
>
> > Just what popped into my head when I read this.
> >
> > -TG
> >
> >
> >
> > > -----Original Message-----
> > > From: d c [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, August 12, 2004 2:51 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: [PHP-WIN] connection: close header
> > >
> > >
> > > Hello,
> > >
> > > I am using php 4.3.4 on windows 2000 with iis 5 and isapi. We
> > > recently switched from asp to php. There is an application
> > > that we have that hits one of the pages to send some info,
> > > and it uses persistant connections. The php page was not
> > > working correctly, and a trace using ethereal showed that the
> > > difference was the "Connection: close" header being sent with
> > > the php page, while the "Connection" header was not present
> > > in the asp page's response. I tried using the latest version
> > > of php, and the header is still being sent.
> > >
> > > Is there a way to get iis to not close the connection with php?
> > >
> > > Thanks,
> > > Dave
> > >
>
> --
> DB_DataObject_FormBuilder - The database at your fingertips
> http://pear.php.net/package/DB_DataObject_FormBuilder
>
> paperCrane --Justin Patrin--
>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
--- End Message ---
--- Begin Message ---
On Fri, 13 Aug 2004 11:07:35 -0700 (PDT), d c <[EMAIL PROTECTED]> wrote:
> The page is for uploading files. The client posts some info about the file, and also
> the file itself. The file is actually sent in chunks. The client is hitting the page
> multiple times until all of the chunks for the file are uploaded. All of the data is
> being sent the the php page, and the first chunk/file info are stored in the db.
> Since the client is trying to re-use the connection, the other chunks are not
> getting sent. It is instead timing-out. Simulating the client in a web browser will
> upload all of the chunks, hitting the page multiple times. I don't know why the
> client was written to try to use persistant connections. It doesn't make sense to me
> to do it that way, but that's the way it is.
>
> With the client, it works on Apache on Windows, but not with IIS. The only
> difference between Apache and IIS is the "Connection: close" header present from
> IIS. The only difference with the asp page and the php page on IIS is the
> "Connection: close" header also.
>
Well, then, the solution is to use Apache instead of IIS. Problem solved. ;-)
I have no idea where you can look for this. Perhaps it is in how PHP
is used with IIS? Don't know if you can use a module vs. CGI with IIS,
but if you can, try. Perhaps it's your build? Have you patched IIS
with all the newest patches? Have you gotten the newest PHP? If yes to
all, it's either a setting in IIS (or PHP) or you just can't do it
with PHP/IIS.
> "Gryffyn, Trevor" <[EMAIL PROTECTED]> wrote:
> Yeah, I understand that bit. Persistent connections to the web server
> make sense to me. What doesn't make sense is why you'd require a
> persisent connection for something to work. The workstation might be
> persistently connected to the web server, but a PHP, ASP or HTML page is
> going to send it's data, then stop. Then you send another request to
> the web server and it sends more data to you. Then you make another
> request and it sends more data. Whether you're persistent or not
> shouldn't make something break as far as I know. It might make things a
> little slower because of having to renegotiate the connection, but since
> HTTP is connectionless by nature, the data it sends doesn't require
> persistent connection.
>
> That's what sessions are for, isn't it?
>
> Not trying to be antagonistic, I just don't understand why a persistent
> connection is required for this to work. Maybe Dave is asking the wrong
> question.
>
> Ok, working with Dave's response to this where he says that he doesn't
> have the option of changing the client, let's focus on the PHP page that
> the application is accessing.
>
> Dave, describe "Not working correctly". What is the nature of the data
> the application sends to the PHP and ASP pages, why does it need a
> persistent connection (again, maybe this isn't the right question to
> solve this problem) and what's the PHP page doing that the ASP doesn't.
> Is it not retrieving all the data or something?
>
> A little more detail might help solve this one.
>
> -TG
>
> > -----Original Message-----
> > From: Justin Patrin [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, August 12, 2004 5:45 PM
> > To: Gryffyn, Trevor
> > Cc: [EMAIL PROTECTED]; d c
> > Subject: Re: [PHP-WIN] connection: close header
> >
> >
> > On Thu, 12 Aug 2004 15:38:02 -0400, Gryffyn, Trevor
> > wrote:
> > > Just tossing out my 2cents.. Maybe there's a way or a
> > reason, but HTTP
> > > connections are, by their nature, connectionless. They
> > send the data
> > > and close the connection. I'm not sure why you'd want to keep a
> > > persistant connection to a specific page.
> > >
> > > There are "Keep Alive" codes you can send that maintain a
> > connection to
> > > the web server so you don't have to go through all the
> > handshaking and
> > > stuff again (ok, I'm not using exact terms here, forgive me.. My
> > > networking is a bit rusty) but that doesn't keep you connected to a
> > > single PHP or HTML or ASP page, just the server.
> > >
> > > Sounds like everything's behaving just as it was designed
> > to and you're
> > > trying to do something really odd. But maybe I'm just not
> > getting what
> > > you're trying to do or something.
> > >
> >
> > Actually, this is something that's supported by the HTTP protocol. You
> > use the same TCP connection (stream) for multiple requests to the
> > webserver. It is a bit strange, but it's supported.
> >
> > Sounds like the OPs webserver isn't allowing the persistent
> > connections to go through. Maybe Apache needs to be configured
> > differently. Or PHP might be doing it. Or maybe the client application
> > should be rewritten to not use persistent HTTP connections. ;-)
> >
> > > Just what popped into my head when I read this.
> > >
> > > -TG
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: d c [mailto:[EMAIL PROTECTED]
> > > > Sent: Thursday, August 12, 2004 2:51 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: [PHP-WIN] connection: close header
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I am using php 4.3.4 on windows 2000 with iis 5 and isapi. We
> > > > recently switched from asp to php. There is an application
> > > > that we have that hits one of the pages to send some info,
> > > > and it uses persistant connections. The php page was not
> > > > working correctly, and a trace using ethereal showed that the
> > > > difference was the "Connection: close" header being sent with
> > > > the php page, while the "Connection" header was not present
> > > > in the asp page's response. I tried using the latest version
> > > > of php, and the header is still being sent.
> > > >
> > > > Is there a way to get iis to not close the connection with php?
> > > >
> > > > Thanks,
> > > > Dave
> > > >
> >
> > --
> > DB_DataObject_FormBuilder - The database at your fingertips
> > http://pear.php.net/package/DB_DataObject_FormBuilder
> >
> > paperCrane --Justin Patrin--
> >
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
>
> !DSPAM:411d0b8b258151191211407!
>
--
DB_DataObject_FormBuilder - The database at your fingertips
http://pear.php.net/package/DB_DataObject_FormBuilder
paperCrane --Justin Patrin--
--- End Message ---
--- Begin Message ---
Did some quick reading:
http://bugs.php.net/bug.php?id=9388&edit=1
"Apache will keep a pconnection open no matter if it's a keep-alive
HTTP connection or not."
also...
"With phpinfo I get 'HTTP_CONNECTION=Keep-Alive'" (in the
"Environment" section)
Maybe have the application hit a PHP script that records the
$_SERVER['HTTP_CONNECTION'] for you and make sure it says "Keep-Alive".
When I hit my PHP scripts, it returns a Keep-Alive, but maybe that's IE
telling IIS to create a persistent connection. I get the same with
Opera. I read that HTTP 1.1 goes persistent by default, but that HTTP
1.0 doesn't. Maybe the application is doing a 1.0 call and Apache
(which, as stated above, always does a persistent connection) and ASP
(which somehow forces persistent? Or maybe just doesn't properly close
the connection due to sloppiness on MS's part or something) manage to
keep it persistent anyway, but PHP triggers the Close, which would be
normal for HTTP 1.0 on IIS.
I was able to change the HTTP_CONNECTION environment variable with:
putenv("HTTP_CONNECTION=Keep-Alive");
Try the following code:
<?php
putenv("HTTP_CONNECTION=Keep-Alive");
phpinfo();
?>
Maybe make a test version of this and have your application hit the page
with and without the "putenv" and record the $getenv("HTTP_CONNECTION")
each time.
Maybe this will force it to be persistent.
Might be some info here too:
http://www.php-faq.com/httpconnections.php#8.1.2.1
Good luck!
-TG
> -----Original Message-----
> From: d c [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 13, 2004 2:08 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [PHP-WIN] connection: close header
>
>
> The page is for uploading files. The client posts some info
> about the file, and also the file itself. The file is
> actually sent in chunks. The client is hitting the page
> multiple times until all of the chunks for the file are
> uploaded. All of the data is being sent the the php page, and
> the first chunk/file info are stored in the db. Since the
> client is trying to re-use the connection, the other chunks
> are not getting sent. It is instead timing-out. Simulating
> the client in a web browser will upload all of the chunks,
> hitting the page multiple times. I don't know why the client
> was written to try to use persistant connections. It doesn't
> make sense to me to do it that way, but that's the way it is.
>
> With the client, it works on Apache on Windows, but not with
> IIS. The only difference between Apache and IIS is the
> "Connection: close" header present from IIS. The only
> difference with the asp page and the php page on IIS is the
> "Connection: close" header also.
>
> "Gryffyn, Trevor" <[EMAIL PROTECTED]> wrote:
> Yeah, I understand that bit. Persistent connections to the web server
> make sense to me. What doesn't make sense is why you'd require a
> persisent connection for something to work. The workstation might be
> persistently connected to the web server, but a PHP, ASP or
> HTML page is
> going to send it's data, then stop. Then you send another request to
> the web server and it sends more data to you. Then you make another
> request and it sends more data. Whether you're persistent or not
> shouldn't make something break as far as I know. It might
> make things a
> little slower because of having to renegotiate the
> connection, but since
> HTTP is connectionless by nature, the data it sends doesn't require
> persistent connection.
>
> That's what sessions are for, isn't it?
>
> Not trying to be antagonistic, I just don't understand why a
> persistent
> connection is required for this to work. Maybe Dave is asking
> the wrong
> question.
>
> Ok, working with Dave's response to this where he says that he doesn't
> have the option of changing the client, let's focus on the
> PHP page that
> the application is accessing.
>
> Dave, describe "Not working correctly". What is the nature of the data
> the application sends to the PHP and ASP pages, why does it need a
> persistent connection (again, maybe this isn't the right question to
> solve this problem) and what's the PHP page doing that the
> ASP doesn't.
> Is it not retrieving all the data or something?
>
> A little more detail might help solve this one.
>
> -TG
>
> > -----Original Message-----
> > From: Justin Patrin [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, August 12, 2004 5:45 PM
> > To: Gryffyn, Trevor
> > Cc: [EMAIL PROTECTED]; d c
> > Subject: Re: [PHP-WIN] connection: close header
> >
> >
> > On Thu, 12 Aug 2004 15:38:02 -0400, Gryffyn, Trevor
> > wrote:
> > > Just tossing out my 2cents.. Maybe there's a way or a
> > reason, but HTTP
> > > connections are, by their nature, connectionless. They
> > send the data
> > > and close the connection. I'm not sure why you'd want to keep a
> > > persistant connection to a specific page.
> > >
> > > There are "Keep Alive" codes you can send that maintain a
> > connection to
> > > the web server so you don't have to go through all the
> > handshaking and
> > > stuff again (ok, I'm not using exact terms here, forgive me.. My
> > > networking is a bit rusty) but that doesn't keep you
> connected to a
> > > single PHP or HTML or ASP page, just the server.
> > >
> > > Sounds like everything's behaving just as it was designed
> > to and you're
> > > trying to do something really odd. But maybe I'm just not
> > getting what
> > > you're trying to do or something.
> > >
> >
> > Actually, this is something that's supported by the HTTP
> protocol. You
> > use the same TCP connection (stream) for multiple requests to the
> > webserver. It is a bit strange, but it's supported.
> >
> > Sounds like the OPs webserver isn't allowing the persistent
> > connections to go through. Maybe Apache needs to be configured
> > differently. Or PHP might be doing it. Or maybe the client
> application
> > should be rewritten to not use persistent HTTP connections. ;-)
> >
> > > Just what popped into my head when I read this.
> > >
> > > -TG
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: d c [mailto:[EMAIL PROTECTED]
> > > > Sent: Thursday, August 12, 2004 2:51 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: [PHP-WIN] connection: close header
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I am using php 4.3.4 on windows 2000 with iis 5 and isapi. We
> > > > recently switched from asp to php. There is an application
> > > > that we have that hits one of the pages to send some info,
> > > > and it uses persistant connections. The php page was not
> > > > working correctly, and a trace using ethereal showed that the
> > > > difference was the "Connection: close" header being sent with
> > > > the php page, while the "Connection" header was not present
> > > > in the asp page's response. I tried using the latest version
> > > > of php, and the header is still being sent.
> > > >
> > > > Is there a way to get iis to not close the connection with php?
> > > >
> > > > Thanks,
> > > > Dave
> > > >
> >
> > --
> > DB_DataObject_FormBuilder - The database at your fingertips
> > http://pear.php.net/package/DB_DataObject_FormBuilder
> >
> > paperCrane --Justin Patrin--
> >
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
>
--- End Message ---
--- Begin Message ---
The PHP Development Team is glad to announce the release of PHP 5.0.1.
This release is a maintenance release consisting mainly of bug fixes. It
also includes new installation docs which are
now auto-generated directly from the PHP Manual (INSTALL in the UNIX source
package, install.txt in the Windows binary distribution both available at
http://www.php.net/downloads.php)
A full list of changes can be found at http://www.php.net/ChangeLog-5.php#5.0.1
Enjoy,
PHP Development Team
--- End Message ---
--- Begin Message ---
I'm getting this message after I install Mambo:
"Can\'t create/write to file \'W:\tmp\#sql_116c_0.MYI\' (Errcode: 2)
SQL=SELECT ROUND(v.rating_sum/v.rating_count) AS rating,
v.rating_count,\na.*, u.name AS author, u.usertype\nFROM mos_content AS
a\nINNER JOIN mos_content_frontpage AS f ON f.content_id = a.id\nLEFT JOIN
mos_users AS u ON u.id = a.created_by\nLEFT JOIN mos_content_rating AS v ON
a.id = v.content_id\nWHERE a.state=\'1\'\n AND a.access <= \'2\'\n AND
(publish_up = \'0000-00-00 00:00:00\' OR publish_up <= NOW())\n AND
(publish_down = \'0000-00-00 00:00:00\' OR publish_down >= NOW())\nORDER BY
f.ordering, a.ordering ASC, a.catid, a.sectionid LIMIT 6"
What does that mean? How can I fix it?
Search at Google, no result.
Can't ask at forums.mamboserver.com cause it's down.
Nobody is replying to my threads at the other forums.
I hope somebody in here can help me.
My Specs:
PHP 5.0.1
Windows XP SP 1
Apache 2.0.50
MySQL 4.0.20d
--- End Message ---
