From 8a6946b18003fae6400a137389f0cb13d0ac4bd6 Mon Sep 17 00:00:00 2001
From: m0gg
Date: Sat, 3 Nov 2007 22:40:09 +0000
Subject: Split nanoHTTP and cSOAP logging

---
 nanohttp/nanohttp-response.h | 44 +++++++++++++++++++++++++++-----------------
 1 file changed, 27 insertions(+), 17 deletions(-)

(limited to 'nanohttp/nanohttp-response.h')

diff --git a/nanohttp/nanohttp-response.h b/nanohttp/nanohttp-response.h
index ddbee78..37f7486 100755
--- a/nanohttp/nanohttp-response.h
+++ b/nanohttp/nanohttp-response.h
@@ -1,5 +1,5 @@
 /******************************************************************
- *  $Id: nanohttp-response.h,v 1.15 2007/01/03 08:33:44 m0gg Exp $
+ *  $Id: nanohttp-response.h,v 1.16 2007/11/03 22:40:11 m0gg Exp $
  *
  * CSOAP Project:  A http client/server library in C
  * Copyright (C) 2003-2004  Ferhat Ayaz
@@ -24,7 +24,15 @@
 #ifndef __nanohttp_response_h
 #define __nanohttp_response_h
 
-/** @defgroup http_response_header_fields Response Header Fields
+/** @file nanohttp-response.h HTTP response handling
+ *
+ * @defgroup NANOHTTP_RESPONSE HTTP response handling
+ * @ingroup NANOHTTP_RESPONSE
+ */
+/**@{*/
+
+/** @defgroup HTTP_RESPONSE_HEADER_FIELDS Response Header Fields
+ * @ingroup HTTP_HEADER_FIELDS
  *
  * The response-header fields allow the server to pass additional information
  * about the response which cannot be placed in the Status-Line. These header
@@ -32,7 +40,6 @@
  * resource identified by the Request-URI. (see RFC 2616)
  *
  * @see	http://www.ietf.org/rfc/rfc2616.txt
- *
  */
 /*@{*/
 
@@ -129,24 +136,25 @@
  */
 #define HEADER_VARY			"Vary"
 
-/**
- *
- * The WWW-Authenticate response-header field MUST be included in 401
- * (Unauthorized) response messages. The field value consists of at least one
- * challenge that indicates the authentication scheme(s) and parameters
- * applicable to the Request-URI.
+/** The WWW-Authenticate response-header field MUST be included in 401
+ * Unauthorized response messages (@ref HTTP_STATUS_401_REASON_PHRASE).
+ * The field value consists of at least one challenge that indicates
+ * the authentication scheme(s) and parameters applicable to the
+ * Request-URI.
  *
- *   WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
+ @verbatim
+   WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
+ @endverbatim
  *
- * The HTTP access authentication process is described in "HTTP Authentication:
- * Basic and Digest Access Authentication" [43]. User agents are advised to take
- * special care in parsing the WWW-Authenticate field value as it might contain
- * more than one challenge, or if more than one WWW-Authenticate header field is
- * provided, the contents of a challenge itself can contain a comma-separated
- * list of authentication parameters.
+ * The HTTP access authentication process is described in "HTTP
+ * Authentication: Basic and Digest Access Authentication". User agents
+ * are advised to take special care in parsing the WWW-Authenticate
+ * field value as it might contain more than one challenge, or if more
+ * than one WWW-Authenticate header field is provided, the contents of
+ * a challenge itself can contain a comma-separated list of
+ * authentication parameters.
  *
  * @see http://www.ietf.org/rfc/rfc2617.txt
- *
  */
 #define HEADER_WWW_AUTHENTICATE		"WWW-Authenticate"
 
@@ -185,4 +193,6 @@ extern void hresponse_free(hresponse_t * res);
 }
 #endif
 
+/**@}*/
+
 #endif
-- 
cgit v1.1-32-gdbae