Add reporting of HTTP state (as well as status) in cupsdReadClient, in hopes of

identifying why two users are experiencing continuous 100-continues after a
client disconnects after an authentication challenge.

diff --git a/scheduler/client.c b/scheduler/client.c
index 20ccf11a9a97dc96fe535eca6c65f6df43421eff..c0dc22a1044460c5d4dfb09e07ae59e31b345af4 100644 (file)
--- a/scheduler/client.c
+++ b/scheduler/client.c
@@ -1,7 +1,7 @@
 /*
  * Client routines for the CUPS scheduler.
  *
- * Copyright 2007-2015 by Apple Inc.
+ * Copyright 2007-2017 by Apple Inc.
  * Copyright 1997-2007 by Easy Software Products, all rights reserved.
  *
  * This file contains Kerberos support code, copyright 2006 by
@@ -812,7 +812,7 @@ cupsdReadClient(cupsd_client_t *con)        /* I - Client to read from */
   * Handle new transfers...
   */
 
-  cupsdLogClient(con, CUPSD_LOG_DEBUG, "Read: status=%d", status);
+  cupsdLogClient(con, CUPSD_LOG_DEBUG, "Read: status=%d, state=%d", status, httpGetState(con->http));
 
   if (status == HTTP_STATUS_OK)
   {