Sender Policy Framework [ SPF ] set up

use it for email verification from mail server like gmail.

before
==>
Received-SPF: neutral (google.com: xxx.xxx.xxx.xxx is neither permitted nor denied by best guess record for domain of donot-reply@xxx.com) client-ip=xxx.xxx.xxx.xxx;

after add dns txt record
==>
v=spf1 a mx -all

==>
Received-SPF: pass (google.com: domain of donot-reply@XXXX.com designates xxx.xxx.xxx.xxx as permitted sender) client-ip=xxx.xxx.xxx.xxx;

http://www.openspf.org/Introduction

Protect page with simple .htaccess and .htpasswd

.htaccess file
-------------------------------
AuthUserFile /full/path/to/.htpasswd
AuthType Basic
AuthName "My Secret Folder"
Require valid-user

.htpasswd
------------------------------
htpasswd .htpasswd young

or edit

young:dXERdeoxy.t.Q

good explain here

http://www.elated.com/articles/password-protecting-your-pages-with-htaccess/

 

this is good app if you don’t have access to the server

http://apps.mathieu-rodic.com/a/.htpasswd-Generator

SSO not working with Safari

SSO doesn’t work correctly. until I found new solution

[ if you know, please comment here]

Safari browser on Apple computers  

[ old version seems okay, but who use old version ]

Workaround: Use other browser or platform

Safari on Windows Vista 

[ safari also hate vista =P ]

 

https://www.uoguelph.ca/ccs/security/internet/single-sign-sso/required-browser-settings

apache points wrong ssl certificate

 

http://wiki.apache.org/httpd/CommonMisconfigurations

NameVirtualHost *:443

<VirtualHost *:443>
  ServerName some.domain.com
  # SSL options, other options, and stuff defined here.
</VirtualHost>

<VirtualHost *:443>
  ServerName some.domain2.com
  # SSL options, other options, and stuff defined here.
</VirtualHost>

Because of the nature of SSL, host information isn’t used when establishing an SSL connection. Apache will always use the certificate of the default virtual host, which is the first defined virtual host for name-based virtual hosts. While this doesn’t mean that you won’t ever be able to access the second virtual host, it does mean your users will always get a certificate mismatch warning when trying to access some.domain2.com. Read more about this at http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2 Also, note that the configuration above isn’t something someone would normally use for SSL, which requires a static, non-shared IP address — NameVirtualHost 127.124.3.53:80 is a more likely format. However, using NameVirtualHost *:443 is common in howtos for Debian/Ubuntu.