Revision history [back]

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 80 (http://<serverip>:81) On port 80 there's another vhost, with other things running

I configured the CALDav server on http://<serverip>:81 but server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address.

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 80 (http://<serverip>:81) On port 80 there's another vhost, with other things running

I configured the CALDav server on http://<serverip>:81 but server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address.

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 80 (http://<serverip>:81) (http://server.ip.addr:81) On port 80 there's another vhost, with other things running

I configured the CALDav server on http://<serverip>:81 http://server.ip.addr:81 but server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address.

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 80 81 (http://server.ip.addr:81) On port 80 there's another vhost, with other things running

I configured the Despite CALDav server running on http://server.ip.addr:81 but http://server.ip.addr:81, server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address.address. The CALDav server is reacheable on port 81 and behaves ok (Ccalendar in Thunderbird on a linux machine synced just fine)

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 81 (http://server.ip.addr:81) (http://server.ip.addr:81)

On port 80 there's another vhost, with other things running

Despite CALDav server running on http://server.ip.addr:81, server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address. address. Obviously, it fails to retrieve anything usefull.

The CALDav server is reacheable on port 81 and behaves ok (Ccalendar (Calendar in Thunderbird on a linux machine synced just fine)

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6

Hello,

I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 81 (http://server.ip.addr:81)

On port 80 there's another vhost, with other things running

Despite CALDav server running on http://server.ip.addr:81, server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address. Obviously, it fails to retrieve anything usefull.

The CALDav server is reacheable on port 81 and behaves ok (Calendar in Thunderbird on a linux machine synced just fine)

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF 2.0.5.6