Janine,
There was some discussion about the fact that that ns_server is not
thread safe and can cause server crashes under moderate load. It's now
documented in the wiki docs, but isn't in the old documentation. It's
not unlikely that your crashes are being caused by running ns_server so
I use the READLINE mode in socat (http://www.dest-unreach.org/socat/)
for this sort of thing, myself...
socat READLINE TCP4:localhost:6767
On 29/06/2004, at 8:56 AM, Brett Schwarz wrote:
--- Dossy [EMAIL PROTECTED] wrote:
On 2004.06.28, Nathaniel Haggard
[EMAIL PROTECTED] wrote:
Is there command
have you tried telneting to the server and including a Host:
steve.festinalente.co.uk header in the request you issue?
what OS is this running on? there should only be one nsd process, but
on linux (I believe) ps shows a distinct process for each thread -
are you saying that there's only a single
And if the client is on the other side of a caching proxy there's still
another layer of buffering between you writing to the socket and an
error being returned.
On 30/03/2004, at 12:05 PM, Dossy wrote:
On 2004.03.29, Bas Scheffers [EMAIL PROTECTED] wrote:
Is it possible to detect the browser has
Manish -
Depending on what you're running inside AOLserver, and your reason for
needing SSL, this may not work the way you expect. Since you're
launching 2 distinct nsd processes, one bound to each of the http and
https ports, any state that is held in the http server won't be
available if a user
If your people are going to be admining the server, and you already
have inhouse Solaris expertise, you could do worse than Solaris/x86...
it's not quite free, but it's pretty close...
On 18/11/2003, at 10:27 AM, Jean-Fabrice RABAUTE wrote:
Hi,
A client want to change it SUN machine to a PC for
On 04/11/2003, at 3:45 AM, Tom Jackson wrote:
Digest Auth seems pretty useless if it requires storing plain text
passwords. That makes a big payoff for breaking into a webserver,
database or whatever stores the passwords.
that's ridiculous - if you can't secure your server enough to protect
the
There seem to be 2 separate arguments going on here - one about the
best way to implement non-Basic authentication in AOLserver, and
another about the usefulness of using Digest in the first place. I'm
going to avoid the implementation related stuff and stick solely to the
utility of Digest auth.
On 04/11/2003, at 12:33 PM, Todd Gillespie wrote:
On Tue, 4 Nov 2003, russm wrote:
that's ridiculous - if you can't secure your server enough to protect
the user passwords then you can't secure it enough to protect the
content protected by those passwords, and you're already up the
proverbial
On 04/11/2003, at 1:35 PM, Dossy wrote:
If you're paranoid, place the authentication mechanism on a machine
that
sits behind some level of network security, and don't let the passwords
pass the wire into unsafe networks at all. Have the webserver call out
to this authentication system passing a
insert at the top of your config file the lines
ns_log Notice [exec /usr/bin/file /usr/local/pgsql/lib/libpq.so.2]
ns_log Notice [exec /usr/bin/file /usr/local/pgsql/lib/libpq.so.2.2]
ns_log Notice [exec /bin/ls -lF /usr/local/pgsql/lib/]
exit
(assuming those paths are correct for your file and
On Wednesday, August 27, 2003, at 01:32 PM, Dossy wrote:
On 2003.08.27, russm [EMAIL PROTECTED] wrote:
That would break a lot of things, I reckon...
Yes! SMTP is fundamentally broken, and that's why it's so easy to send
spam in a way that's hard to track down and easy to forge
Spoofing [ns_conn peeraddr] at the IP level is difficult if your
platform has random enough IP initial sequence numbers, and can be
blocked at your router with an explicit rule to drop inbound packets on
the WAN interface that have a source address on your LAN.
There has also been talk on the list
Hi all,
I'm wondering what is the status of any DAV server projects people are
working on for AOLServer. I'm aware of the mod_dav port that Musea is
working on, and I've seen mention here of an nsdav from the AOL folks
based on Dossy's work, but as far as I can tell Musea's work is
restricted to
On Friday, August 1, 2003, at 07:54 AM, Rob Mayoff wrote:
+-- On Jul 31, Roberto Mello said:
| - Readline support for nscp.
You could just get a better client program. For example, connecting to
nscp from inside Emacs can give you editing and history support.
If you have a separate
On Wednesday, July 16, 2003, at 10:36 AM, Gustaf Neumann wrote:
PS: with the log-file-change in the aolserver, there is a
potential small security leak. The proxy MUST bock
requests that have already X-Forwarded-For set (easily
configurable in pound). otherwise, it is possible that the
wrong
16 matches
Mail list logo
