|
Tutorial Books by Herong - References by Others
I am so happy to see that my tutorial books have been referenced by many articles and books on the Internet.
I am listing few examples here. -- Herong
Dovecot SSL warning (not error)
Subject: [coba-e:07286] Re: Dovecot SSL warning (not error) [update2]
Date: Sep 28, 2006
Author: Patrick Giagnocavo
Source: http://bluequartz.org/ml/archive/coba-e/7200/7286.html
>> If you move a certificate from one server to another you may have
>> to get a new one re-issued.
>>
>> Certificate security is pretty tight to prevent fraud sights wrongly
>> being identified as kosher sites.
>
> I'm very familiar with Thawte SSL certs in a web context but not
> others and can say
> that Thawtes can be moved without issue as long as the domain used
> upon is as issued.
Are you sure that it isn't the case, that the "private" server.key file
must also be moved or copied, along with the issued SSL cert file?
> Well, it's technically doable at least with self signed certs so I'm
> half happy. Just
> need to work out how to get dovecot to use certs for the domain in
> question rather than
> just the one pointed to in the conf file. Maybe dovecot.conf allows
> environmental vars
> so certs could be referred to with local relative paths to a
> users/domains "home"?
>
I have found this page very helpful:
http://www.herongyang.com/crypto/openssl_verify.html
Actually the whole site is helpful when dealing with SSL!
Cordially
Patrick Giagnocavo
UTF-8 support
Subject: [Bugs] [plogger] #122: UTF-8 support
Date: Mar 15, 2006
Author: Victor
Source: http://lists.plogger.org/pipermail/bugs/2006-March/000390.html
I've realized that the UTF8 character set isn't really support in Plogger.
I'm talking about 2.1 version, but seems that version 3 is affected too.
Although Plogger ''_install.php'' script creates the MySQL tables with the
UTF-8 character set properly, the information is not really stored in
UTF-8 as far as I know. I realized that because the RSS feed generated
with special characters (''ñ,á,é,'' and so on) didn't work properly,
and get complaints about the use of invalid characters (''ñ'' and
so on). Looking in the database, I see that the information itself isn't
been stored in really UTF-8.
In my Plogger version I fixed this problem doing the next things:
'''1)''' The Admin backend XHTML is not in UTF-8. For that I added the
line
<meta http-equiv="Content-Type" content="txt/html; charset=utf-8" />
in the XHTML generated, and to make sure:
header("Content-Type: text/html; charset=utf-8");
With this we're sure the XHTML generated is in UTF-8, but we can't assure
the information from the forms is been sent to the MySQL server in UTF-8.
See step # 2
'''2)''' To make sure about the last point mentioned I added the next
line:
$rs = run_query("SET NAMES 'utf8'");
(I'm not going to explain here this command, don't worry ;), but you can
see more info here:
[http://www.herongyang.com/php/non_ascii_mysql_2.html])
So, Ok, we're storing properly the utf-8 information in the Database,
but... why the hell my XML isn't valid yet? Let's look at step # 3
...
Re: XHTML ou HTML
Subject: Re: XHTML ou HTML
Date: Feb 17, 2006
Author: Davis Zanetti Cabral
Source: Google Group - ArqHP - Arquitetura de home pages
Walter Araujo wrote:
> :D
> e em jsp? como seria?
Sei que pode se usar assim:
<jsp:directive.page contentType="application/xhtml+xml"/>
<jsp:directive.page contentType="text/html"/>
Mas como fazer condicional dá uma olhada aqui ó:
http://www.herongyang.com/jsp/response_header.html
Acho que pode ajudar.
Click here to see the older references.
| 