Retrieving a changeset results in an empty page
|Reported by:||Christian Boos||Owned by:||Jonas Borgström|
I was trying to get a changeset page, but instead I got an empty page (0 bytes), no error.
That was for Markup:changeset:104, but I don't think the changeset module is the culprit, I guess it could have happened with another page as well. It's not the first time I'm seeing this, hence the ticket.
Too bad I didn't have LiveHTTPHeaders running, but at least I looked for the server status immediately after the "error", so it can be possible to retrieve something in the log.
Apache Server Status for www.edgewall.org ... Current Time: Saturday, 22-Jul-2006 12:14:51 CDT Restart Time: Wednesday, 19-Jul-2006 16:20:44 CDT ... CPU Usage: u163.71 s13.69 cu2.04 cs0 - .0734% CPU load 2.71 requests/sec - 33.7 kB/second - 12.4 kB/request 3 requests currently being processed, ... Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request ... 17-0 - 0/0/37114 . 2.62 8 0 0.0 0.00 435.85 18.104.22.168 markup.edgewall.org GET /changeset/104 HTTP/1.1