Picasa 網路相簿的 Name Tag 功能
作者:cross 日期:2008-10-22 10:58
Darwin Streaming Server 是一個 open source 的 streaming server
作者:cross 日期:2008-09-30 18:52
Welcome to Darwin Streaming Server, the open source version of Apple's QuickTime Streaming Server technology that allows you to send streaming media to clients across the Internet using the industry standard RTP and RTSP protocols. Based on the same code base as QuickTime Streaming Server, Darwin Streaming Server provides a high level of customizability and runs on a variety of platforms allowing you to manipulate the code to fit your needs.
nginx 是一個 Web 伺服器，類似於 Apache
作者:cross 日期:2008-09-20 13:58
免費網頁掃毒工具 Dr.Web anti-virus link checker
作者:cross 日期:2008-09-18 14:01
apache + mod_gnutls 達到單一IP多個domain使用SSL服務
作者:cross 日期:2008-09-17 19:26
Apache 無法在單一IP建置SSL給多個 Virtual Host (name-based)使用，也就是說 SSL 服務只能在 ip-based 底下使用，
Apache 官網 http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts 說明了一切
http://help.directadmin.com/item.php?id=89Why can't I use SSL with name-based/non-IP-based virtual hosts?
The reason is very technical, and a somewhat "chicken and egg" problem. The SSL protocol layer stays below the HTTP protocol layer and encapsulates HTTP. When an SSL connection (HTTPS) is established Apache/mod_ssl has to negotiate the SSL protocol parameters with the client. For this, mod_ssl has to consult the configuration of the virtual server (for instance it has to look for the cipher suite, the server certificate, etc.). But in order to go to the correct virtual server Apache has to know the Host HTTP header field. To do this, the HTTP request header has to be read. This cannot be done before the SSL handshake is finished, but the information is needed in order to complete the SSL handshake phase. Bingo!
http://httpd.apache.org/docs/2.0/ssl/ssl_faq.htmlWhy do I need an owned IP for my own SSL certificate? Last Modified: Oct 26, 2005, 3:20 pm
The reason you must have your own IP address when you want to use your own SSL certificate (when you don't want the server wide shared certificate) is because of the way SSL and apache (httpd) works.
For name based webhosting (when many domains are on one IP) the web browser will pass the name of the domain being requested inside the httpd headers along with the request. This way, apache knows which domain you are trying to access even though there are many domains on that one IP address.
When you do the same thing through an SSL connection, the connection has to be made *before* the request can be sent. In this connection, the certificate is passed. The only information that apache knows before the request is made is which IP the connection is being made to. It has to be able to know which certificate to send before the request is made, thus you can't use mutiple certificates on the same IP (if you do, apache will use the first certificate listed which DA will always set to the server shared certificate for shared IPs).
If you want to use your own certificate, it must be the first certificate listed. This wouldn't work for a shared IP, because there would multiple domain wanting this status, and the first certificate would the one shown. For this resaon the shared certificate is always used on a shared IP. For your certificate, DA will aknowledge the IP as being 'owned' and will remove the server shared certificate as the first cert to be loaded, thus your certificate will be loaded instead.
無法瀏覽 CGI 程式 (perl) malformed header from script. Bad header=<html>
作者:cross 日期:2008-09-16 06:30
/var/log/httpd/error_log
malformed header from script. Bad header=<html>
ref: http://cs.uccs.edu/~cs301/perl/perl.htm
Basically the web server complains that the wrongHello.cgi returns a web page without proper header such as "content-type: text/html " before the body of the web page <html>HelloWorld!. The header is required as the CGI secification or CGI protocol between the CGI process running the wrongHello.cgi and that of the web server. For more detail see the CGI web page.
The above hello.pl is perl script can be run standalone. It is not a CGI perl script since it did not follow the CGI protocol. In order to make that as a CGI perl script, we need to add the following two lines after #!/usr/bin/perl
use CGI qw(:standard);
print header();or
print "content-type: text/html ";
Google 瀏覽器
作者:cross 日期:2008-09-02 12:43
