php-general Digest 14 Nov 2010 05:30:03 -0000 Issue 7035
Topics (messages 309473 through 309477):
question about preventing polling for more than once
309473 by: ФêÏ
309474 by: [email protected]
309476 by: Andre Polykanine
Re: php running as module or cgi?
309475 by: John Hicks
confusion about the file extension for php interpreter to interpret
309477 by: ФêÏ
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 ---
I noticed that some websites such as
polldaddy<http://polldaddy.com/account/home.php> has
fascinating poll service. And I am just curious about how it prevents user
from polling the same poll for more than once. Or more accurately, I am a
dynamic IP user. And I found that if I have polled once for a certain poll
and after some time, I changed my IP when I got connected to the Internet
again, I cannot poll the previous one for the second time. So I am confused
how polldaddy <http://polldaddy.com/account/home.php> can figure out that I
have polled even if I had changed my IP. Is there any way to achieve that?
Thanks in advance.
--- End Message ---
--- Begin Message ---
Have you checked for any cookies left by that website?
Thanks,
Ash
http://www.ashleysheridan.co.uk
----- Reply message -----
From: "肖晗" <[email protected]>
Date: Fri, Nov 12, 2010 15:14
Subject: [PHP] question about preventing polling for more than once
To: <[email protected]>
I noticed that some websites such as
polldaddy<http://polldaddy.com/account/home.php> has
fascinating poll service. And I am just curious about how it prevents user
from polling the same poll for more than once. Or more accurately, I am a
dynamic IP user. And I found that if I have polled once for a certain poll
and after some time, I changed my IP when I got connected to the Internet
again, I cannot poll the previous one for the second time. So I am confused
how polldaddy <http://polldaddy.com/account/home.php> can figure out that I
have polled even if I had changed my IP. Is there any way to achieve that?
Thanks in advance.
--- End Message ---
--- Begin Message ---
Hello ??,
Try to clean up your cookies. Maybe they set a cookie on your
computer.
--
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: http://twitter.com/m_elensule
Facebook: http://facebook.com/menelion
----- Original message -----
From: ?? <[email protected]>
To: [email protected] <[email protected]>
Date: Friday, November 12, 2010, 5:14:49 PM
Subject: [PHP] question about preventing polling for more than once
I noticed that some websites such as
polldaddy<http://polldaddy.com/account/home.php> has
fascinating poll service. And I am just curious about how it prevents user
from polling the same poll for more than once. Or more accurately, I am a
dynamic IP user. And I found that if I have polled once for a certain poll
and after some time, I changed my IP when I got connected to the Internet
again, I cannot poll the previous one for the second time. So I am confused
how polldaddy <http://polldaddy.com/account/home.php> can figure out that I
have polled even if I had changed my IP. Is there any way to achieve that?
Thanks in advance.
--- End Message ---
--- Begin Message ---
On 11/11/2010 02:14 PM, Didier Gasser-Morlay wrote:
On 11/11/2010 12:04 PM, Richard Quadling wrote:
On 11 November 2010 00:46, Al<[email protected]> wrote:
Briefly, what are the trade offs on a typical shared host?
I've done a little research and can't seem to find anything outstanding
either way.
Seems like as an Apache module is faster. This argument makes sense.
CGI is more secure, this argument doesn't seem too persuasive to me.
Maybe
I'm missing something.
Thanks....
As a module, any misbehaving script is running within the same space
as all the other scripts. If a script is able to knock out PHP (for
any reason), all the script go.
With CGI, they are run in separate spaces. No direct communication
(unless the scripts are sharing memory by some way). If a script
knocks out PHP, that script dies. Everything else keeps on going.
The main downside to CGI (as I understand things), is that for each
invocation of the script, PHP has to do the complete build up and tear
down every single time. For every single script.
With FastCGI, when the server starts, a pool of ready to go php
instances are created. So a script is called, the build up part is
already done.
In terms of speed, I'd guess you'd have to be working pretty hard to
see the difference between module/isapi and fast-cgi.
If I am not mistaken, An apache module can even bring down the whole
web server if it really misbehaves.
So this leaves the choice between CGI & FatsCGI.
CGI setup/teardown is only an issue for site with a fairly high
traffic. It really depends on the type of site you intend to build.
To me, the main security issue with mod_php in a virtual domain
configuration is that it runs as the apache user and therefore any php
code can read any files accessible to apache. If you have clients
maintaining their own php code, they can access the code (and passwords
and databases) of your other clients.
I've never used cgi but I hope that it allows you to avoid this problem.
Am I correct?
--John
--- End Message ---
--- Begin Message ---
Apache defaultly use php interpreter to execute files ended with '.php'
extension.
How can I change this rule?Can I change the default extension to any
arbitrary name? Such as .PHP or .Php and so on.
And I am using Ubuntu/Linux, Apache2 and php5.
Thanks very much!
--- End Message ---
