We recently had a client that uses our product complain that their server
wasn't coming up. Upon further examination it was determined that in
Win32TransService::Win32TransService() if this constructor can't find an
"InternetEncoding" for any codepage that it finds in the registry it just
panics.
I noticed that at the beginning of the code that if it can't open the
"MIME\\Database\\Charset" registry key that it just defaults to using the
intrinsic encodings supported by the parser itself.
The diffs below illustrate my change, most noticeably:
1) While iterating thru the registry the first time looking for codepages
that aren't aliases, if it can't open a key, just continue
2) If while iterating thru the registry the second time looking for aliased
codepages, if it can't open the key, just continue
Sorry that I don't have a diff of the two version of the file. My original
was taken from the Version 1.3 release code, it doesn't look like anything
has changed in this file from 1.3 to the latest source.
Andrew
Win32TransService.cpp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
