Making Light :: Tiresome technical issues :: comments

Tiresome technical issues

We're aware that individual archive pages for posts with many comments are cutting off long before their end. For instance,...

Tiresome technical issues -- comment #1 from "Charles Dodgson"

Thu, 31 Aug 2006 00:25:21 -0500

The response served up for a

curl 'http://nielsenhayden.com/makinglight/archives/007781.html'

is 196,608 bytes in length --- which happens to be exactly 192 kilobytes. This is a suspiciously round number (more obviously so in hex --- 0x30000).

This proves nothing, but suggests that the moral equivalent of an Apache LimitRequestBody directive might be involved...

]]>

Posted August 31, 2006 12:25 AM by "Charles Dodgson"

Tiresome technical issues -- comment #2 from P J Evans

Thu, 31 Aug 2006 00:33:48 -0500

I was having Open Thread 69 cut off at about #182 - Patrick, that's one of your comments. (The thread wasn't like that yesterday. I wonder what got reset.)

]]>

Posted August 31, 2006 12:33 AM by P J Evans

Tiresome technical issues -- comment #3 from Dave Bell

Thu, 31 Aug 2006 01:02:24 -0500

Also noticed yesterday:

Linking via the new comments list in the sidebar went to a particular comment, possibly somewhere around the numbers reported (I didn't take notes, alas), although the whole page did download.

]]>

Posted August 31, 2006 1:02 AM by Dave Bell

Tiresome technical issues -- comment #4 from Clifton Royston

Thu, 31 Aug 2006 01:23:08 -0500

I'm fairly sure this was working normally yesterday, the day before at worst. I'm aware that's not much help, but you can at least ask the hosting company if they have made any webserver configuration changes in that period of time.

]]>

Posted August 31, 2006 1:23 AM by Clifton Royston

Tiresome technical issues -- comment #5 from "Charles Dodgson"

Thu, 31 Aug 2006 02:02:01 -0500

To clarify (and partially correct!) my earlier observation, the URL is that for Open Thread 69, and 'curl' is a program which can be used to save the HTTP response to a file. The fact that it returns a short file containing a round number of bytes suggests that something might be truncating the server's response at that round number of bytes --- but an Apache LimitRequestSize directive wouldn't do that; it limits the size of the request, not the response. (Duh). On the other hand, if the ISP is using squid to front-end their Apaches (or the equivalent), a squid reply_body_max_size setting would have this effect (if I'm reading the docs right!).

Sorry about the error, but too late to correct, I guess...

]]>

Posted August 31, 2006 2:02 AM by "Charles Dodgson"

Tiresome technical issues -- comment #6 from Lisa

Thu, 31 Aug 2006 06:45:20 -0500

It appears to be a timing issue; the server essentially runs out of time to complete the request.

I am suspicious, probably without reason, of the numbering of the posts.

]]>

Posted August 31, 2006 6:45 AM by Lisa

Tiresome technical issues -- comment #7 from Patrick Nielsen Hayden

Thu, 31 Aug 2006 07:46:20 -0500

Mystery solved: we were using 999 MB of our 1000 MB quota of disk space. Our provider, having kindly figured this out for us, has increased our quota. I've just now run a full-site rebuild and everything looks fine. Let me know if it isn't.

Not for the first time, I strongly recommend Hosting Matters for your weblog hosting needs.

]]>

Posted August 31, 2006 7:46 AM by Patrick Nielsen Hayden