David-Development / Task-Sync

5 stars 0 forks source link

Port not used from URL #32

Open peter-rindfuss opened 10 years ago

peter-rindfuss commented 10 years ago

I'm trying to connect to https://myserver:8443/calendar, but it seems that the port 8443 is not used. Rather, the server's log shows connection attempts to port 443. This makes Task Sync unusable to me.

David-Development commented 9 years ago

Thank you for the report. Sounds weird. I think the app should use the custom port but anyway I'm going to check it. Is it possible to create a test account for me? (I can verify than that it's working for your server - credentials via email please: david-dev@live.de).

peter-rindfuss commented 9 years ago

Am 2014-11-09 um 15:33 schrieb David-Development:

Thank you for the report. Sounds weird. I think the app should use the custom port but anyway I'm going to check it.

Hi,

Thanks for your reply.

Good news is that it works now.

I have to apologize for the port stuff: Our Apache server always reports 443 for https, 80 for http. They call it "canonical port" as opposed to "physical port".

I still don't know why I could not log in initially (tried many times with several accounts). The Caldav server is Davical on Debian, and it works fine so far with all sorts of clients.

Cheers, Peter

David-Development commented 9 years ago

This issue can be closed, or not?