php-general Digest 18 Apr 2009 17:50:39 -0000 Issue 6074
Topics (messages 291659 through 291660):
Re: Setting Up A Directory For HTTPS Secure Certificate
291659 by: Michael A. Peters
Re: What is wrong with this code
291660 by: Reese
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 ---
revDAVE wrote:
GOAL : no one will be able to get to HTTPS directory VIA HTTP.....
So I make this little tester page that seems to work.... Later I'll add auto
redirect.... Is this the kind of thing to add to various pages? Is there a
better way to do this?
I do a separate document root for secure content, and use a separate sub
domain (though that isn't required).
They way only content in the secure document root is served via https
and content outside the secure domain never is served via https.
I do listen on port 80 of the secure subdomain - but it forwards to the
http site:
<VirtualHost *:80>
ServerName secure.shastaherps.org
RewriteEngine On
RewriteRule ^(.*)$ http://www.shastaherps.org/ [R]
</VirtualHost>
--- End Message ---
--- Begin Message ---
9el wrote:
*Note:* It is worth noting that the mail() function is not suitable for
larger volumes of email in a loop. This function opens and closes an SMTP
socket for each email, which is not very efficient.
For the sending of large amounts of email, see the » PEAR::Mail, and »
PEAR::Mail_Queue packages.
*
Note:* The following RFCs may be useful: » RFC 1896, » RFC 2045, » RFC 2046,
» RFC 2047, » RFC 2048, » RFC 2049, and » RFC 2822.
Copy from PHP Manual.
How is "larger volumes of email" defined where mail() is concerned?
Is a number specified anywhere? I didn't see one on the manual page
for mail().
Reese
--- End Message ---
