> But now I know apache and mod_dav better that a week ago, so I'll check
> if it is possible to reuse COPY method with Destination header.
It is possible, but I cannot find a function that tells me if a char *
value represents current hostname/ip address so I could tell when to use
remote or lo
William A. Rowe, Jr. wrote:
That's correct. Windows utf-8 code page 65001 or so is only a psuedo
page
in all older and (afaik) newer flavors of windows). So it's returning
this
character in the local code page, can't represent it, and falls back
on '?'.
Yup, and that's what our assumption
Stusynski, Dan wrote:
The corrupt DN is coming back with a hex value of 3F (question mark)
when the sequence should be hex values e68891 (or 346\210\221) in
decimal).
That's correct. Windows utf-8 code page 65001 or so is only a psuedo page
in all older and (afaik) newer flavors of windows).
Eric,
The corrupt DN is coming back with a hex value of 3F (question mark)
when the sequence should be hex values e68891 (or 346\210\221) in
decimal).
Dan
-Original Message-
From: Eric Covener [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2008 10:12 AM
To: dev@httpd.apache.org
Sub
On Thu, Jul 17, 2008 at 11:00 AM, Andy Wang <[EMAIL PROTECTED]> wrote:
> Basically the dn returned in the following two lines is already mangled with
> the ? character:
> entry = ldap_first_entry(ldc->ldap, res);
> dn = ldap_get_dn(ldc->ldap, entry);
>
> Thanks,
> Andy
What's the byte sequ
Sequence of events are as follows:
ldap_search_ext_s to an ldap URL and search base that does not contain
UTF-8 characters.
manager bindDn and bindPw do not contain UTF-8 charaters (all are
US-ASCII) only. The attribute being searched for (uid) does not contain
UTF-8 characters as well.
For
On Wed, Jul 16, 2008 at 4:55 PM, Andy Wang <[EMAIL PROTECTED]> wrote:
> the case where we're seeing this none of the arguments contain anything
> other than US ASCII characters. If you're ldap_search_ext_sW call contains
> only US-ASCII but the returned DN contains UTF-8 shouldn't this still work
Hi,
up to the release of apache 2.2.4 the 'timeout' parameter of the
BalancerMember directive would affect only the connection timout to the
backend servers. This allowed to set reasonably small timeout
values(let's say 1 or 2 seconds) in a scenario where the balancer and
the backends would si
Dnia 17-07-2008 o godz. 9:14 Julian Reschke napisał(a):
> Rafał wrote:
> > Hello!
> >
> > I've done first part of the job - there is now a FETCH method that works
> > in that way:
> >
> > FETCH /destination/path HTTP/1.1
> > Source: http://webdav.example.com/webdav-resource-to-fetch
> > ...
>
>
Rafa%u0142 wrote:
Hello!
I've done first part of the job - there is now a FETCH method that works
in that way:
FETCH /destination/path HTTP/1.1
Source: http://webdav.example.com/webdav-resource-to-fetch
...
I'm not sure it's a good idea to define a new method for that.
If people *really* t
10 matches
Mail list logo
