Hi!
I am using ap_rwrite() and ap_rflush() for sending data to the client.
In some cases the Browser (IE 5.0) does not get the information (or
won't display it; or does not get everything). But with mozilla 1.3a it
works very well.
Any suggestions, what the error can be?
Thanks in advance,
Jos
Hi,
I will try to draw the problem i have...
I am using mod_auth_ldap or mod_auth_radius for apache 2.0 (apache
2.0.44-dev)
when i setup a authentication with ldap, i do
AuthName authentication
AuthType basic
(a misterious directive i need and i can't remember)
AuthLDAPEnable ON
this
Hi -
This is more of a question for the users list, not the dev list, but i'll
answer below:
>-- Original Message --
>Date: Wed, 29 Jan 2003 19:15:56 +0100
>From: Estrade Matthieu <[EMAIL PROTECTED]>
>[Wed Jan 29 19:02:00 2003] [error] [client 192.168.100.3] (9)Bad file
>descriptor: Could not ope
Josef Zellner wrote:
Hi!
I am using ap_rwrite() and ap_rflush() for sending data to the client.
In some cases the Browser (IE 5.0) does not get the information (or
won't display it; or does not get everything). But with mozilla 1.3a
it works very well.
Any suggestions, what the error can be?
* Midhun Chandran wrote:
> I am seeing the following problem on dav-enabled apache 2.0.35 build on
> solaris 2.8.
[...]
> I am still investigating this problem. Any clue on the cause of the
> problem or possible fix will
> be appreciated.
hmm, 2.0.35 is quite outdated. have you tried current 2.0.
* Mladen Turk wrote:
> This is the virtual file system module,
> meaning that you can serve context from non-file systems.
>
> Currently it only supports zip files, but has already added support
> for gzip and bzip archives.
Cool thing in general. But shouldn't we consider a pluggable mod_autoin
This builds on the work Craig Rodrigues did for apr-util; it uses the same
logic and mostly the same methodology.
Cheers,
-Thom
Index: buildconf
===
RCS file: /home/cvspublic/httpd-2.0/buildconf,v
retrieving revision 1.29
diff -u -r1
We operate a WebDav site, currently on
Apache 2.0.42, but operating in the same
manner since 2.0.16...
...Our users are able to create, move,
copy, and delete files.
We have Apache running as user "nobody"
and group "nobody" (but started as root)...
...we are using the "worker" model.
The all
--On Thursday, January 30, 2003 00:48:43 +0100 André Malo <[EMAIL PROTECTED]>
wrote:
Cool thing in general. But shouldn't we consider a pluggable
mod_autoindex instead? I'm thinking of something similar to mod_dav:
mod_autoindex - base, contains all the display stuff and an interface for
--On Wednesday, January 29, 2003 23:55:29 + Thom May
<[EMAIL PROTECTED]> wrote:
+if [ ! -d "$apr_src_dir" -o ! -f "$apr_src_dir/build/apr_common.m4" ];
then echo ""
-echo "You don't have a srclib/apr/ subdirectory. Please get one:"
+echo "You don't have a copy of the apr source.
* Justin Erenkrantz wrote:
> At this point, I think we might want to consider something more general
> that has been a pet peeve of ours: pluggable core filesystems. Look in the
> ROADMAP file on 'making apache repository-agnostic.' -- justin
oops, read this some time ago, but somehow forgot ab
* Frank Faubert wrote:
> Add "CookieTracking on" to the end of the default httpd.conf file, start up
> Apache and look at the headers for "/" -- only one cookie. Now copy
> /tmp/apache/htdocs/index.html.en to /tmp/apache/htdocs/index.html and look
> at the headers for "/". I get two cookies for
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2002/10/31 05:57:52 $]
Release:
1.3.28-dev: In development
1.3.27: Tagged September 30, 2002. Announced Oct 3, 2002.
1.3.26: Tagged June 18, 2002.
1.3.25: Tagged June 17, 2002. Not re
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2003/01/27 17:50:43 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related proj
Allow mod_dav to do weak entity comparison function rather than a
strong
entity comparison function. (i.e. it will optionally strip the W/
prefix.)
That doesn't really follow the spirit of etag validation in HTTP.
In theory, the client is not allowed to use weak etags for anything
other tha
--On Wednesday, January 29, 2003 10:18 PM -0800 "Roy T. Fielding"
<[EMAIL PROTECTED]> wrote:
Allow mod_dav to do weak entity comparison function rather than
a strong
entity comparison function. (i.e. it will optionally strip the
W/ prefix.)
That doesn't really follow the spirit of et
16 matches
Mail list logo