21

Just switched some downloads over to the Akamai CDN network and I'm seeing some strange stuff in the log files they deliver. A number of entries have the status code 000. When I asked them they said that 000 is the status when the client disconnects without transferring the entire file. Since 000 doesn't appear to be a valid HTTP response code (from the RFC), I have to wonder if that's right.

skaffman
  • 381,978
  • 94
  • 789
  • 754
Mitchell V
  • 781
  • 1
  • 5
  • 13
  • 1
    It's their logfile, they can make 000 mean whatever they want it to mean. Do you have a reason to think they're lying to you? – Wooble Mar 20 '12 at 17:18
  • It seems to be some kind of custom extension from Akamai. So far I think the client will get the response code 200. – rekire Mar 20 '12 at 17:19
  • Wooble : not lying to me but I've had plenty of cases where the people on the front lines of support don't always have all of the information. FWIW, the log file is *supposed* to be a standard "combined" log format file. It'd be pretty strange for them to break from the standards, especially since those error codes will throw any analytic software off (that's how I learned about the problem in the first place). – Mitchell V Mar 20 '12 at 18:32

3 Answers3

23

There's a knowledge base article (requires login) which lists their log values:

Log Delivery Services (LDS) LDS will show a 000 for any 200 or 206 responses with a client abort: the object was served correctly from the origin or edge, but the end-user terminated the connection/transaction before it completed.

This is indeed a custom status because the standard log format doesn't include a field which can indicate a client abort.

Sri Sankaran
  • 7,494
  • 4
  • 35
  • 46
Chris Adams
  • 4,786
  • 27
  • 28
13

000 is a common code to use when no HTTP code was received due to a network error. According to a knowledge base article for Amazon CloudFront, 000 also means that the client disconnected before completing the request for that service.

Kevin Borders
  • 2,766
  • 25
  • 31
3

It normally means: No valid HTTP response code (ie: Connection failed, or was aborted before any data happened).

I would guess that their are either network issues or Akamai isn't managing their webservers correctly.

keithhackbarth
  • 6,681
  • 3
  • 22
  • 31
  • 1
    It's pretty hard to believe that Akamai would do anything non-standard with logging seeing as they're one of the biggest (and oldest) CDN providers out there. Anything is possible I guess... – Mitchell V Mar 20 '12 at 18:32