Summary: | Can't login to website since Leopard 10.5.3 update | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tom Pelaia II <pelaiata> |
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | mrowe, pelaiata |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Mac | ||
OS: | OS X 10.5 | ||
URL: | https://snsapp1.sns.ornl.gov/Logbook/WebObjects/Logbook.woa |
Description
Tom Pelaia II
2008-06-02 12:04:30 PDT
> If someone from Apple would like to observe the problem, I can provide a read > only account in confidence. There were no material WebKit changes between Safari 3.1.1 and Mac OS X 10.5.3. This makes it likely that the problem is in an underlying framework that WebKit uses, such as CFNetwork. I think it would be best to file a bug report at http://bugreport.apple.com/ so that it can be assigned to the relevant team. Bug reports filed via bugreport.apple.com are not publicly accessible, so feel free to include account information if it will help in reproducing the problem. As mentioned by Mark, it would be indeed best to file this at bugreport.apple.com. Please make sure to provide as much detail on your network setup as you can - i.e. whether there is a proxy involved, and if it is, what software and what version. Testing with a different internet provider would also help (but don't hesitate to file the bug even if getting this additional information is not possible). Yes, I've filed a bug report with Apple's bug reporter. It includes information that will allow them to reproduce the bug if they wish to test it. (In reply to comment #2) > As mentioned by Mark, it would be indeed best to file this at > bugreport.apple.com. Please make sure to provide as much detail on your network > setup as you can - i.e. whether there is a proxy involved, and if it is, what > software and what version. Testing with a different internet provider would > also help (but don't hesitate to file the bug even if getting this additional > information is not possible). > <rdar://problem/5979488> Now closing as INVALID per our process, as a non-WebKit issue. This will continue to be tracked by Apple internally. |