18304 2008-04-03 14:11:21 -0700 https + proxy = crash 2008-04-03 14:50:33 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Mac OS X 10.5 RESOLVED INVALID P2 Major --- 0 jzeephat webkit-unassigned oldest_to_newest 76266 0 jzeephat 2008-04-03 14:11:21 -0700 We use Microsoft Forefront (also called ISA) proxy server at my job. Every https connection crashes both Safari and WebKit and recent nightlies. Other apps that use Webkit+https (like Adobe's app registration) crash as well. Apple's own Problem Report app fails, but does not crash. From forums and Apple support site, I know others are experiencing the same behavior, but I didn't see it reported here. From what I gather, Webkit https requests through a proxy just stalls on 10.4.11, it does not crash. (Sorry, I'm a newb here, and am just guessing at how to do this...) Every error report following a crash, looks as below - the last line is always the same in the crashed thread. (I've not included the whole thing - if I should, let me know.): Thread 3 Crashed: 0 com.apple.CoreFoundation 0x926d53bc CFDataGetBytePtr + 64 1 com.apple.CFNetwork 0x931778e8 _NtlmCreateClientResponse + 588 2 com.apple.CFNetwork 0x9318da2c _CFHTTPAuthenticationUpdateFromResponse + 1008 3 com.apple.CFNetwork 0x9314aee8 updateAuth + 200 4 com.apple.CFNetwork 0x9314a934 updateForHeaders + 160 5 com.apple.CFNetwork 0x9314a6e0 httpConnectionResponseStreamCB + 108 6 com.apple.CFNetwork 0x9314a5f8 connectionResponseCallBack + 116 7 com.apple.CoreFoundation 0x9271b8c8 _CFStreamSignalEventSynch + 340 8 com.apple.CoreFoundation 0x9270a34c CFRunLoopRunSpecific + 1112 9 com.apple.Foundation 0x91e74344 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 280 10 com.apple.Foundation 0x91e1d4f4 __NSThread__main__ + 1004 11 libSystem.B.dylib 0x92d9db98 _pthread_start + 316 76271 1 mrowe 2008-04-03 14:50:33 -0700 This is not a WebKit issue. The crash is inside CFNetwork, a system framework, and is already tracked in Radar. Closing as INVALID to indicate that this is not a WebKit issue.