Bug#578216: ocsigen: server does not respond

[Paul Pelzl <pelzlpj@gmail.com>]

On Sun, Apr 18, 2010 at 1:10 AM, Stéphane Glondu <glondu@debian.org> wrote:
>> Is this the expected behavior when the port is configured as
>> "<port>80</port>"?  The documentation is not clear on this point.
>
> Actually, the expected behaviour was to listen on both IPv6 and IPv4,
> but that changed with net.ipv6.bindv6only (which changed from 0 to 1 in
> Debian recently). This is fixed upstream, but I didn't applied the patch
> in the Debian package because it can be easily worked around by using
> "<port>*:80</port>".
>
> The documentation is there (look for "<port>"):
>
>  http://ocsigen.org/ocsigenserver/config
>
> I tried to be as explicit as possible about this point. Feel free to
> propose something better (I am also upstream and can fix the website).

The documentation is explicit about the qualified forms
"<port>*:80</port>" and "<port>[::]:80</port>", but the unqualified
form of "<port>80</port>" is not addressed explicitly.  It would be
helpful to have an additional sentence that explains this case
(although I guess it might not have helped me today if the behavior
was due to a recent Debian change).

Thanks for the help.

Paul