Bug 18304
| Summary: | https + proxy = crash | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jerry Zeephat <jzeephat> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Major | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Jerry Zeephat
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
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.