426 reputation
1722
bio website bitlucid.com
location New York, NY
age 34
visits member for 4 years, 10 months
seen Jul 3 at 22:22

I'm hirable at bitlucid.com, train ninjas at ninjawars.net, do crazy art when I can at dnaexmosn.deviantart.com, and code stuff at github.com/tchalvak

Code in:

  • html/css (come on, tell me webdesign isn't coding, dare ya)
  • javascript
  • php

Want to code in: - Clojure

Want to code on: - node.js

Formerly Tchalvak


Feb
20
comment Increased number of 408 Request Timeouts for null on a webserver
Fair enough, the browser predictive optimization one seems like it may well fit the situation, especially since the error logs match. So I'll have to verify that myself later. Thanks.
Feb
20
accepted Increased number of 408 Request Timeouts for null on a webserver
Feb
19
revised Increased number of 408 Request Timeouts for null on a webserver
Adding a few new tags.
Feb
18
revised Increased number of 408 Request Timeouts for null on a webserver
deleted 12 characters in body
Feb
18
revised Increased number of 408 Request Timeouts for null on a webserver
added 120 characters in body
Feb
18
comment Increased number of 408 Request Timeouts for null on a webserver
I posted a longer sampling of the most recent 408 requests into the pastebin link. The hits are relatively infrequent, throughout the day.
Feb
18
revised Increased number of 408 Request Timeouts for null on a webserver
added 201 characters in body
Feb
13
revised Increased number of 408 Request Timeouts for null on a webserver
edited title
Feb
13
comment Increased number of 408 Request Timeouts for null on a webserver
Potentially related question: serverfault.com/questions/247051/…
Feb
13
comment Increased number of 408 Request Timeouts for null on a webserver
I've lowered it to 150 seconds, though I guess that will only increase the number of timeouts, of course, but I guess at least the requests that timeout wont hold onto resources.
Feb
13
comment Increased number of 408 Request Timeouts for null on a webserver
Looks like it is the rediculously high number of 300 seconds: # # Timeout: The number of seconds before receives and sends time out. # Timeout 300
Feb
13
comment Increased number of 408 Request Timeouts for null on a webserver
The "408 request timeout null: 694 times" and "a total of 125 sites probed the server" messages are from the logwatch log summarizing app, which emails me out info about the server logs on a daily basis. The others are entries from a grep of /var/log/apache2/access.log I also clarified in my question now.
Feb
13
revised Increased number of 408 Request Timeouts for null on a webserver
Linked logwatch, clarified as much as I can.
Feb
13
revised Increased number of 408 Request Timeouts for null on a webserver
Minor typo fix
Feb
13
awarded  Promoter
Feb
12
awarded  Popular Question
Feb
5
awarded  Tumbleweed
Jan
29
revised Increased number of 408 Request Timeouts for null on a webserver
edited title
Jan
29
revised Increased number of 408 Request Timeouts for null on a webserver
edited title
Jan
29
revised Increased number of 408 Request Timeouts for null on a webserver
added 585 characters in body