Hello,
I've inherited a DAViCal installation, and due to some completely
braindead "enterprise" clients still in use, I am tasked with
simplifying the URLs. Don't ask. Anyway, point is that user A's
resource Foo needs to be a accessible as
`https://caldav.example.org/A/Foo`.
This works, using nothing other than
```
Alias / /usr/share/davical/htdocs
FallbackResource /davical/caldav.php
```
but there is a remaining problem, namely that when DAViCal returns
URLs to itself, it forces /caldav.php/ back into the path, e.g.
```
/.well-known/caldav ? /caldav.php/A/Foo
```
and this is because the [well-known handler sets `$force_script =
true` when calling
`ConstructURL`](https://gitlab.com/davical-project/davical/-/blob/master/inc/well-known.php#L18).
I am sure there are other places, where this happens, and reading
the source suggests to me that there is no way around this, despite
[advice to set
`$c->base_url`](https://bugzilla.mozilla.org/show_bug.cgi?id=605201#c4)
(which does not work).
I've even tried to hide http://localhost/davical/caldav.php behind a
transparent proxy, but that doesn't work either.
Has anyone managed to actually expose DAViCal without exposing
`caldav.php` in the URL?
--
@martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net
"vulgarity is simply the conduct of other people."
-- oscar wilde
spamtraps: madduck.bogus@madduck.net
I've inherited a DAViCal installation, and due to some completely
braindead "enterprise" clients still in use, I am tasked with
simplifying the URLs. Don't ask. Anyway, point is that user A's
resource Foo needs to be a accessible as
`https://caldav.example.org/A/Foo`.
This works, using nothing other than
```
Alias / /usr/share/davical/htdocs
FallbackResource /davical/caldav.php
```
but there is a remaining problem, namely that when DAViCal returns
URLs to itself, it forces /caldav.php/ back into the path, e.g.
```
/.well-known/caldav ? /caldav.php/A/Foo
```
and this is because the [well-known handler sets `$force_script =
true` when calling
`ConstructURL`](https://gitlab.com/davical-project/davical/-/blob/master/inc/well-known.php#L18).
I am sure there are other places, where this happens, and reading
the source suggests to me that there is no way around this, despite
[advice to set
`$c->base_url`](https://bugzilla.mozilla.org/show_bug.cgi?id=605201#c4)
(which does not work).
I've even tried to hide http://localhost/davical/caldav.php behind a
transparent proxy, but that doesn't work either.
Has anyone managed to actually expose DAViCal without exposing
`caldav.php` in the URL?
--
@martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net
"vulgarity is simply the conduct of other people."
-- oscar wilde
spamtraps: madduck.bogus@madduck.net