Hi, This took me several hours to find out, therefore I think it should be documented.
I needed it to provide IPv6 support, because the default socket is
created for IPv4 only.
Best wishes,
Arne
From 0feec9c9d4de01aad66e5d891602e42436e61400 Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide <b...@draketo.de>
Date: Sat, 10 Nov 2018 11:19:36 +0100
Subject: [PATCH] document that a custom socket must already be bound
---
doc/ref/web.texi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index c8fc488b7..3cd7d0245 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -1739,7 +1739,8 @@ state.
@end deffn
The default web server implementation is @code{http}, which binds to a
-socket, listening for request on that port.
+socket, listening for request on that port. If you provide a custom
+socket, you must take care to bind it to the right address.
@deffn {HTTP Implementation} http [#:host=#f] @
[#:family=AF_INET] @
--
2.19.1
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
signature.asc
Description: PGP signature
