0 Replies Latest reply: Jul 19, 2010 8:06 AM by 807573 RSS

    CORE7002: authenticated doc - forced refresh: and then HTTP2228

    807573
      I see this error message in the errors log which is then followed by HTTP2228 content-length mismatch errors till that object is expired/removed from the cache.
      [19/Jul/2010:02:50:18] info (15712): CORE7002: authenticated doc - forced refresh: http://host.server.com/
      [19/Jul/2010:02:51:10] info (15712): CORE7002: authenticated doc - forced refresh: http://host.server.com/
      [19/Jul/2010:02:51:10] warning (15712): for host 99.103.23.238 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:52:17] warning (15712): for host 206.192.70.102 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:52:47] warning (15709): for host 99.103.23.238 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:52:53] warning (15712): for host 206.192.70.102 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:52:59] warning (15712): for host 62.81.205.97 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:57:35] warning (15712): for host 70.114.170.151 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      [19/Jul/2010:02:58:26] warning (15712): for host 124.124.3.6 trying to GET /, finish-response reports: HTTP2228: Response content length mismatch (560 bytes with a content length of 2560)
      Has anyone come across this issue and if yes, is there a workaround is it a setting that can disable this?

      Right now, i have a script scanning the logs for either the 'forced refresh' or the HTTP2228 entries and then remove the object in question but clearly not ideal.

      Thanks
      JB