On Fri, Oct 17, 2003 at 12:07:17AM +0200, Johannes Hromadka wrote:
> >> I tired to ad my servers certificate to SSL_CERT_DIR, but lynx does
> >> not accept it. It only accepts the certificate of the issuer of my
> >> servers cert.
> >
> >Well, if it is so, this should be classified as a bug in lynx.  Can
> >you provide necessary files so that this becomes reproducible?
> 
> I'm not sure if it is a bug or just designed this way.

> For testing I can provide a certificate for your server and my root certificate.
> Do you have an apache server for testing? 
> Send me the full hostname and I can generate a certificate. I also can send you my 
> config files for reference.

I'm confused again.  Is your server's certificate a secret?  If not,
they why not provide it, so we can check whether connecting to your
server works on other architectures.

> >Lynx is not a web browser.  E.g., it understands file: links too.  ;-)
> >I would classify it as a "URI space" browser.  And if there is an URL
> >type for S-Mime, it is reasonable to expect that lynx would support it
> >too [but I have no idea whether S-Mime is expressable via URIs].

> But there are much more other URIs, like ftp, gopher, news, snews, ldap, sip, h323,..

Lynx understands most URI types I know about.  There was some
discussion of allowing snews:; do not remember the resolution.  I
never tried ldap, sip, h323, I know nothing about them.

> Just realised that lynx is able to follow news: URIs :-o 
> But it has problems with German national characters.

Do not think there is any problem with lynx here.  However, news:
semantic does not has a way to specify the charset.  Try going to `o'
and setting the default "assumed" charset...  Oh, maybe my logic to
automaticaly switch VIO charset is not supported with news:!  Try to
switch the charset from the default one (auto) to your current
charset.

Or maybe you just do not have defaulting to `auto'?  Change the
display charset to auto, then save `o'ptions.

Yours,
Ilya

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]

Reply via email to