| Summary: | proxy authenfication doesn't work | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | azymut |
| Component: | general | Assignee: | Thiago Macieira <thiago> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ahartmetz, blshadow, mkyral, patrick.noffke, thiago, tlovasic |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Disabled proxy auth setting
Proxy Auth TCP Dump Summary Packet data for single proxy auth attempt. Packet data for HTTPS connection via proxy |
||
|
Description
azymut
2009-07-07 17:23:41 UTC
Precision: I'm using a squid proxy. Still not working under kde 4.3 This problem is kde-related providing this proxy works perfectly with arora. I'm testing KDE 4.3 and I cannot reproduce the problem. I get the password prompt. My proxy is Squid 3.0, with Basic authentication. Created attachment 36124 [details]
Disabled proxy auth setting
I can confirm it. See screenshot above. I'm behind ISA proxy and I never got the authentication dialog. Other applications like FF, TB. and Psi works correctly. Maybe I miss some dependency. I have the same problem. I am also behind an ISA firewall, and absolutely nothing happens. I have more information on this. Essentially, like Marian, I am also behind ISA proxy which is essentially NTLM proxy. While playing with the proxy settings, I have actually discovered that the HTTPS proxy setting works (I do get prompted for credentials and I do get to the given site) while the HTTP proxy doesn't. The tcpdump shows that konqueror received a "proxy requires authentication" msg but nothing appears on the screen. forgot to mention that this is fedora 11 with kde 4.3.1... Hi, I can confirm that the auth. dialog is shown for https and not shown for http. But I still could not connect on https: proxy authorisation failed. Maybe it is because I have to authorize as <domain>\<user_name>. Is this supported? Or how should be entered? I have the same problem with KDE 4.3.4 on Fedora 12. If I manually specify the proxy (specify the server:port for HTTP and select use same proxy server for all protocols), then I get the authentication dialog for HTTPS but not for HTTP. I am able to enter my proxy username and password for HTTPS and connect successfully. But for HTTP, konqueror just displays in the status bar: "<hostname> contacted. Waiting for reply..." I believe our proxy server uses NTLM authentication, but I'm not sure how to determine this. # rpm -q kdebase kdebase-4.3.4-1.fc12.x86_64 Note to Marian, we use a windows domain, but for the proxy server, I just have to enter my username (no domain), and I can connect via HTTPS. *** This bug has been confirmed by popular vote. *** Created attachment 39777 [details]
Proxy Auth TCP Dump Summary
I started wireshark, then started Konqueror. I set the display filter to tcp.srcport==80 or tcp.dstport==80. This file shows the packet summary lines. Repeated attempts are made to connect via the proxy.
Created attachment 39778 [details]
Packet data for single proxy auth attempt.
This is the same capture as for the TCP dump summary, except I selected one of the repeated attempts where konqueror sends the NTLMSSP_NEGOTIATE, and the proxy server responds with NTLMSSP_CHALLENGE, and in wireshark I chose "Follow TCP stream."
Note: For both attachments that I added, I selected to "Manually specify the proxy settings," and our proxy server is http://qgproxy.qg.com:80. I selected to use the same proxy server for all protocols. Created attachment 39779 [details]
Packet data for HTTPS connection via proxy
This contains the packet data when I connect via HTTPS to the login page for my credit union. The proxy authentication seems to fail on the first attempt but then succeeds with the authentication supplied in CONNECT message.
Again, I selected "Follow TCP stream" in wireshark, then saved off the data (stream content) to a text file.
It still not works in KDE 4.4.5. I'll test 4.5 soon, but probably will not work as well :-( So I tested KDE 4.5.0 and it works. *** This bug has been marked as a duplicate of bug 155707 *** |