[Citadel Development] (no subject)
dothebart: I've got good news and bad news. The good news is that GroupDAV is fixed. It works just fine with KOrganizer again. The bad news is that I had to roll back the code. Something broke during the conversion to doxygen, and I couldn't figure out exactly where, so I had to roll back all of the groupdav*.[ch] files to just before the doxygen conversion began. You're certainly welcome to put those changes back in, but test GroupDAV with KOrganizer every step of the way to make sure we don't end up with the same problem again. I'm very sorry that I had to undo your work. But again, it is working now. So anyway, once it was working, I tested again with the server-absolute URL's instead of global-absolute, and unfortunately it broke KOrganizer. KOrg seems to want globally absolute URL's. I did, however, put all of the "host prefix" outputs into a single function which gets called from all the other places, so we could think about putting in a "force this prefix" string in there.
[Citadel Development] (no subject)
Hrm.. the -f option didn't help my chat problem.
[Citadel Development] (no subject)
once again after tiny mce is booted a paste with newlines: PROPFIND /groupdav/ HTTP/1.1Host: 127.0.0.1:2000User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.3 (like Gecko) (Debian package 4:3.4.3-2)Pragma: no-cacheCache-control: no-cacheAccept: text/html, image/jpeg, image/png, text/*, image/*, */*Accept-Encoding: x-gzip, x-deflate, gzip, deflateAccept-Charset: iso-8859-1, utf-8;q=0.5, *;q=0.5Accept-Language: enAuthorization: Basic d2dvOm9obXlnOHQ=Depth: 1Content-Type: text/xml; charset=utf-8Content-Length: 142Max-Forwards: 10Via: 1.1 tucholsky.ty.newthinking.deX-Forwarded-For: 192.168.2.234X-Forwarded-Host: tucholsky.ty.newthinking.deX-Forwarded-Server: tucholsky.ty.newthinking.de
[Citadel Development] (no subject)
PROPFIND /groupdav/ HTTP/1.1 Host: 127.0.0.1:2000 User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.3 (like Gecko) (Debian package 4:3.4.3-2) Pragma: no-cache Cache-control: no-cache Accept: text/html, image/jpeg, image/png, text/*, image/*, */* Accept-Encoding: x-gzip, x-deflate, gzip, deflate Accept-Charset: iso-8859-1, utf-8;q=0.5, *;q=0.5 Accept-Language: en Authorization: Basic d2dvOm9obXlnOHQ= Depth: 1 Content-Type: text/xml; charset=utf-8 Content-Length: 142 Max-Forwards: 10 Via: 1.1 tucholsky.ty.newthinking.de X-Forwarded-For: 192.168.2.234 X-Forwarded-Host: tucholsky.ty.newthinking.de X-Forwarded-Server: tucholsky.ty.newthinking.de
[Citadel Development] (no subject)
Oo! I didn't know about the -f option... maybe *that* explains why I've been experiencing weirdness with the chat page...
[Citadel Development] (no subject)
>if i have an apache proxying it seems as if the groupdav urls built >just contain 127.0.0.1 as hostname. Fixed. When we have WebCit sitting behind an Apache proxy, we already require the "-f" option to be specified, which causes it to honor the "X-Forwarded-For:" header. Now we honor the "X-Forwarded-Host:" header as well.
[Citadel Development] (no subject)
the actual installation: [EMAIL PROTECTED]:~# netstat -lnp |grep webservertcp0 0 0.0.0.0:20000.0.0.0:* LISTEN 13218/webserver root 13218 0.0 0.7 20828 3672 ?Ss Jan26 0:05 /usr/sbin/webserver -f -p2000 uds /var/run/citadel/ 127.0.0.1 ssl.conf Description: Binary data
