On Tue, 21 Jan 2014 14:13:22 +0100, Sönke Ludwig wrote:

Am 18.01.2014 22:22, schrieb Øivind Loe:

It seems like, after upgrading from 0.7.16 to 0.7.18 (I think), my simple webserver has stopped working. (...)

How does vibe.d master behave there? The log output looks like it's
stuck reading the file from disk (or yield()ing). There have been a
few issues with yield that are now fixed, maybe those are somehow
responsible for this (although it doesn't seem very likely).

Did not help to move to master.. When I abort the request, there is some more input from vibed.. See the last lines: 

--------------------
Got request header.
persist: true
handle request (body 0)
route match: / -> GET /
opened file ./ui/index.html with 867 bytes as 34
---------------------
HTTP server response:
---------------------
HTTP/1.1 200 OK
Content-Encoding: gzip
Server: vibe.d/0.7.18
Date: Fri, 24 Jan 2014 02:35:31 GMT
Keep-Alive: timeout=10
Last-Modified: Fri, 29 Nov 2013 20:57:01 GMT
Etag: "B0E3F852E9AFA7F3C57AB03825B9235E"
Expires: Sat, 25 Jan 2014 02:35:31 GMT
Cache-Control: max-age=86400
Content-Type: text/html
Transfer-Encoding: chunked
---------------------
evbuffer_add (fd 32): 338 B
bufferevent_flush
socket 32 write event (false)!
Timer event true/true
Creating new fiber...
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Timer event true/true
Timer event true/false
Socket event on fd 32: 17 (7FBFDC003E88 vs 7FBFDC003E88)
Connection was closed (fd 32).
Timer event true/true
Timer event true/false
data wait timeout
 -> timeout = true
Client didn't send the initial request in a timely manner. Closing connection.
task out (fd 33).
Closing socket 33...
...socket 33 closed.
task finished.
Timer event true/true
Timer event true/false