Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sogo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246732
Title:
Acces
Actually, rather than commenting out stanzas, one should just fix the
directives to use the correct statement in the sogo.conf:
Require all granted
# Explicitly allow caching of static content to avoid browser specific
behavior.
# A resource's URL MUST change in order to have the cl
And just for the record: the reason why the default configuration doesn't work,
is that the most recent Ubuntu versions ship with Apache 2.4 and it new
authorization model. Even though mod_access_compat is enabled, the Order/Allow
directives don't work, because the base Apache configuration in U
It *is* a bug in the sogo package, because this is the standard Apache
configuration that ships with Ubuntu. If sogo doesn't work with it out
of the box, it *has* to provide an Apache configuration stanza.
** Changed in: sogo (Ubuntu)
Status: Invalid => New
--
You received this bug notifi
The apache configuration is not installed by default because it is just
an example that must be adapted before it can be used. That your apache
configuration denies access to the web frontend resources is a bug in
your apache configuration and not in the sogo package.
** Changed in: sogo (Ubuntu)
