Does anyone know where I can find a prebuilt (i.e. ps/pdf) version of the
flood manual? Thanks
jerome
Are any of the other flood profiles implemented? The DESIGN document
mentions other profiles such as random, sequenced, and chaining;
however I can't seem to find any other documentation on them, nor can I
find anything about them in the code. Any insight would be much
appreciated. Thanks
jerome
In case a SSL connection fails because a certificate is
expired, or a CRL is unavailable, etc., the browser receives a SSL error that
results in a cryptic technical error displayed to the user - sometimes only an
error number like in Firefox. In such a situation, the SSL connection could be
[EMAIL PROTECTED] wrote:
In case a SSL connection fails because a certificate is expired, or a
CRL is unavailable, etc., the browser receives a SSL error that results
in a cryptic technical error displayed to the user - sometimes only an
error number like in Firefox. In such a situation, the
If I'm not wrong, I think what you're looking for is in
${openssl_home}/crypto/x509/x509_vfy.h
Look for :
#define X509_V_OK 0
[... error codes ]
My remark was that I see no variable containing the error code, so i have to
check a string
- Original Message -
From: Stephane Bailliez
Maybe another possibility (?) is to extend the
SSL_CVERIFY_OPTIONAL_NO_CA to also suppress other types of error, although this
may be dangerous as, in this case the certificates are accepted and no error is
generated. Can we still trap the error later ?
To investigate ...
- Original
That feature avoids the addition of charset=iso-8859-1 on certain
error responses. But its dependence on SetEnv means it only works if
the request reached fixup hook before failing. That means it can't
be used like this:
Redirect /Contacts http://www.example.com/contacts
Location /Contacts
+1 from me :)
How appropriate would a 2.0/2.1 patch be as well?
On Apr 29, 2005, at 1:19 PM, Jeff Trawick wrote:
That feature avoids the addition of charset=iso-8859-1 on certain
error responses. But its dependence on SetEnv means it only works if
the request reached fixup hook before failing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think that most other developers agree that 2.1.x/trunk has enough
features for a 2.2.x GA branch.
I believe 2.1.x is a moving target.
I think it is hard to stabilize a moving target.
I believe we should always keep trunk open for development.
I
On 4/29/05, Jim Jagielski [EMAIL PROTECTED] wrote:
+1 from me :)
How appropriate would a 2.0/2.1 patch be as well?
You tell me. I'm certainly willing to work up a 2.1 patch.
I have to confess to ignorance about the scope of the problem.
Somebody tells me this suppress-error-charset feature
10 matches
Mail list logo
