Bug 25386
| Summary: | Proxy user authentication information not sent | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Olivier Devaux <odevaux> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | mrowe |
| Priority: | P2 | ||
| Version: | 525.x (Safari 3.2) | ||
| Hardware: | All | ||
| OS: | OS X 10.5 | ||
Olivier Devaux
When the user uses Safari to surf the internet via a proxy, which requires user to authenticate against the proxy, Safari does not send the proxy authentication data in any new TCP sessions even when the browser is not closed. This behavior is different from other browsers such as IE and Firefox. Since the browser does not send the proxy authentication data, the proxy sends an HTTP 407 reply. At this time, the browser then includes the authentication information.
The browser should have sent the proxy authentication data in all HTTP requests after the user authenticates against the proxy, even for those requests that are sent using new TCP sessions, as long as the requests are from the same browser instance.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
Proxy support is handled by the CFNetwork framework that Mac OS X provides and that WebKit uses for network access. You should file a bug report against CFNetwork at <http://bugreport.apple.com/>. This bug will be closed to indicate that the problem was outside of WebKit.
Olivier Devaux
The behavior is the same on windows. Is this expected ?
Mark Rowe (bdash)
Safari on Windows also uses Apple's CFNetwork, so yes.