Can AOLServer's ns_sock send out multipart/alternative emails? If so, how
does this work? I'm trying to create a situation whereby users who can read
html in their emails see the marked-up page, while users whose email clients
are incompatible with html or who have html email capability turned of
Nevermind. I figured this out by doing a more restrictive a google search
for "email multipart/alternative AOLServer", and reading this:
http://ccm.redhat.com/asj/mime/
the trick was having the boundary= part in the content-type header itself.
scott
-Original Message-
From: Scott Laplant
On Tuesday 11 March 2003 13:23, Mark Page wrote:
> This document provides technical information which may be useful for
> developers who are porting a AOLserver module from an earlier version of
> AOLserver to AOLserver 4.0. This document is located under 'C
> Development' of the Documentation se
On Tue, 11 Mar 2003, Tom Jackson wrote:
> Tomasz Kosiak wrote:
>
> >Thta is not exactly true. They adjust both url filters and handlers
> >registered in urltrie. You can easily enhance fastpath registered proc to
> >take pageroot from arg given to registration and then you can serve static
> >con
This document provides technical information which may be useful for developers who are porting a AOLserver module from an earlier version of AOLserver to AOLserver 4.0. This document is located under 'C Development' of the Documentation section of this site, or by pointing your browser at http:/
Ok, so maybe I was not seeing the *exact* same problem ;) I was just
seeing the error messages in the log. I had seen the "server error"
message on the browsers some time ago, but I expected the error
messages to also go away. I guess it must be the OpenSSL exploit
then... any way to check and make
Note that you will see some EOFs in the log files that are normal and
aren't due to failures. I see them all the time because we're using
client certs -- MSIE makes a connection, realizes the server wants a
client cert, cuts the conn (EOF), asks the user which client cert they
want to use, then mak
Tomasz Kosiak wrote:
Thta is not exactly true. They adjust both url filters and handlers
registered in urltrie. You can easily enhance fastpath registered proc to
take pageroot from arg given to registration and then you can serve static
content from virtual host pageroot. You can achive that and
So I switched session caching on last night and when I checked the logs
this morning, I see that there were a couple of new EOF during SSL
handshake errors. Checking the access log, it looks like something funny
was going on; Non-existent files being accessed and such. I think Dossy
might be rig
I only see up to the first ctrl-L on a number of files in sf:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/aolserver/aolserver/nsd/fastpath.c?rev=1.18&content-type=text/vnd.viewcvs-markup
Is anyone else having this problem?
--Tom Jackson
I. To remove yourself from this list:
Send a message
On Mon, 10 Mar 2003, Jerry Asher wrote:
> Apart from that your options are to hack the code and modify nsvhr to
> only take over a part of the urlspace, or better, to have the master
> register for some urlspace that it will serve.
My recently proposed ns_register_proxy command does exactly this
On Mon, 10 Mar 2003, Tom Jackson wrote:
> I like the additional exposed api's very much. However, the virtual
> hosting changes to the core are unnecessary and don't have the entire
> effect required for virtual hosting. The main problem is the virtual
> hosting changes only adjust the filters, t
On 2003.03.10, William Scott Jordan <[EMAIL PROTECTED]> wrote:
>
> Error: nsopenssl: EOF during SSL handshake
I never used to see this error (and I have session caching turned off)
until the recent OpenSSL exploits came about.
Ever since then, every couple of hours I'll see this in my logs ... th
I need to know the browser type, version and strength (e.g. MSIE 5.5
128-bit, Netscape 4.7 40-bit...).
Oscar, when you say you're seeing the exact same problem, do you mean
you're seeing both the error message and the browser is failing on the
first connect?
/s.
On Tuesday, March 11, 2003, at 08:4
I'm seeing the exact same problem, however I have ServerSessionCache set to true. I'm
using
nsopenssl 2.1. What could the problem be?
This is the nsopenssl part of my aolserver config file:
-
ns_section "ns/server/${servername}/module/nsopenssl"
ns_param ServerPort ${ht
15 matches
Mail list logo
