Yahoo is not totally HTTP compliant ... what else is new?

An article in Cisco's support wiki caught my attention today: it claims that Cisco routers could deny access to yahoo.com because Yahoo!'s web servers emit invalid chunked encoding. Interesting ... so I've started Fiddler and opened Yahoo!'s home page. This is what I've got:

HTTP/1.1 200 OK
Date: Sun, 14 Sep 2008 13:42:11 GMT
P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE GOV"
Cache-Control: private
Vary: User-Agent
Set-Cookie: IU=deleted; expires=Sat, 15 Sep 2007 13:42:10 GMT; path=/; domain=.yahoo.com
Set-Cookie: FPCM=deleted; expires=Sat, 15 Sep 2007 13:42:10 GMT; path=/
Set-Cookie: D=_ylh=X3oDMTFkbmtlMG9nBF9TAzI3MTYxNDkEcGlkAzEyMjEzOTczMjEEdGVzdAMwBHRtcGwDaW5kZXgtbA--; path=/; domain=.yahoo.com
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip

7b17   

As you can see there are actually three blanks after the chunk length, which is a clear violation of section 3.6.1 of RFC 2616 (HTTP); the chunk length should be followed by semicolon (for chunk extensions) or CRLF. I'm not really surprised; the crappy implementation of Frontpage extensions on Geocities (and the fact that they wanted to charge me for it) pushed me toward my own web site six years ago.