Closed
Bug 242457
Opened 21 years ago
Closed 21 years ago
NTLM should use nspr logging instead of printf with a special ifdef
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
VERIFIED
FIXED
mozilla1.8alpha1
People
(Reporter: Biesinger, Assigned: Biesinger)
References
()
Details
Attachments
(1 file)
6.69 KB,
patch
|
darin.moz
:
review+
darin.moz
:
superreview+
|
Details | Diff | Splinter Review |
Assignee | ||
Updated•21 years ago
|
Target Milestone: --- → mozilla1.8alpha
Assignee | ||
Comment 1•21 years ago
|
||
I had to rewrite the hexdump function (PrintBuf); nspr would have written each
char on its own line...
Assignee | ||
Comment 2•21 years ago
|
||
("rewrite" as in "make slightly less trivial changes than to the rest of the file")
Assignee | ||
Updated•21 years ago
|
Attachment #147652 -
Flags: superreview?(darin)
Attachment #147652 -
Flags: review?(darin)
Comment 3•21 years ago
|
||
Comment on attachment 147652 [details] [diff] [review]
like this
>Index: nsNTLMAuthModule.cpp
>+#ifdef MOZ_LOGGING
>+#define FORCE_PR_LOG
>+#endif
>+#include "prlog.h"
I don't know that this needs to be enabled in release builds. Do you
know of cases where it would be helpful to have this in release builds?
I believe HTTP logging logs the WWW-Authenticate challenges, and so we
can always use netwerk/test/ReadNTLM to generate the same kind of output
that this file produces.
Therefore, my recommendation is to not define FORCE_PR_LOG.
>+#ifdef PR_LOGGING
>+PRLogModuleInfo *gNTLMLog = PR_NewLogModule("NTLM");
If it is indeed valid to instantiate these at file scope, then maybe we
should be doing that everywhere else too. What do you think?
>+#else
>+#define LOG(x)
>+#define LOG_ENABLED() PR_FALSE
> #endif
I don't think you should need to define LOG_ENABLED outside of PR_LOGGING.
If you do need LOG_ENABLED outside of PR_LOGGING, then it probably means
that you should wrap the conditional in a #ifdef PR_LOGGING anyways.
> static void PrintFlags(PRUint32 flags)
> PrintBuf(const char *tag, const PRUint8 *buf, PRUint32 bufLen)
> static void PrintToken(const char *name, const void *token, PRUint32 tokenLen)
s/Print/Log/ perhaps? I think these would be better as Log*
r+sr=darin with those changes. Thanks for writing this patch.
Attachment #147652 -
Flags: superreview?(darin)
Attachment #147652 -
Flags: superreview+
Attachment #147652 -
Flags: review?(darin)
Attachment #147652 -
Flags: review+
Assignee | ||
Comment 4•21 years ago
|
||
(In reply to comment #3)
> I don't know that this needs to be enabled in release builds. Do you
> know of cases where it would be helpful to have this in release builds?
sorry... this is a leftover from testing this patch.
> >+#ifdef PR_LOGGING
> >+PRLogModuleInfo *gNTLMLog = PR_NewLogModule("NTLM");
>
> If it is indeed valid to instantiate these at file scope, then maybe we
> should be doing that everywhere else too. What do you think?
hm... several modules do this already:
http://lxr.mozilla.org/seamonkey/search?string=PR_NewLogModule
e.g. cookieservice, jpeg decoder, stopwatch.h, parts of content, parts of gfx,
webshell...
> I don't think you should need to define LOG_ENABLED outside of PR_LOGGING.
> If you do need LOG_ENABLED outside of PR_LOGGING, then it probably means
> that you should wrap the conditional in a #ifdef PR_LOGGING anyways.
hm, looks like I only use it inside an ifdef PR_LOGGING block. ok, I'll remove
that define.
> > static void PrintFlags(PRUint32 flags)
> > PrintBuf(const char *tag, const PRUint8 *buf, PRUint32 bufLen)
> > static void PrintToken(const char *name, const void *token, PRUint32 tokenLen)
>
> s/Print/Log/ perhaps? I think these would be better as Log*
ok, will do that.
Assignee | ||
Comment 5•21 years ago
|
||
Checking in nsNTLMAuthModule.cpp;
/cvsroot/mozilla/security/manager/ssl/src/nsNTLMAuthModule.cpp,v <--
nsNTLMAuthModule.cpp
new revision: 1.9; previous revision: 1.8
done
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
V:
(you can verify your own "code change" bugs when you include the checkin info...)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•