Opened 10 years ago

Closed 4 months ago

#496 closed defect (cantfix)

Yahoo will not work through HTTP proxy which only allows 80 and 443

Reported by: dthatcher Owned by: sulabh.dev
Milestone: Component: Yahoo!/Yahoo! JAPAN
Version: 2.0 Keywords: yahoo proxy proxies
Cc: James, alexbischoff

Description

Latest 2.0.0 beta 7 on XP SP2: I have tried many different servers and ports for Yahoo. The only port that works is 80, but even though the app seems to be able to talk to the yahoo server on that port, it does not connect. The proxy settings require the port for connection to the proxy server to be at 80. Yahoo Messenger works fine on the same system and network. Other protocols work fine.

Attachments (1)

error.txt (1.2 KB) - added by James 7 years ago.

Download all attachments as: .zip

Change History (22)

comment:1 Changed 10 years ago by lschiere

  • Component changed from pidgin (gtk) to libpurple
  • Owner set to marv

comment:2 in reply to: ↑ description Changed 10 years ago by marv

I believe this to be because we don't implement yahoo over http, and because the proxy isn't allowing a connect command (or we don't try one when the port is 80).

comment:3 Changed 10 years ago by lschiere

  • Milestone set to 2.0.2

comment:4 Changed 9 years ago by seanegan

  • Component changed from libpurple to Yahoo!

comment:5 Changed 9 years ago by yule

Is there any update on this issue? Pidgin 2.3.1 on XP SP2 still doesn't connect to yahoo via a http proxy. IM works fine, but things like buddy icons get left out.

comment:6 Changed 9 years ago by rekkanoryo

  • Resolution set to fixed
  • Status changed from new to closed

This should be fixed for 2.4.0.

comment:7 Changed 9 years ago by yule

Sorry, but it still doesn't work for me. I need to connect to a http proxy on port 8080, and Pidgin still gives an error.

comment:8 Changed 9 years ago by Sim-on

  • Milestone changed from 2.4.0 to 2.4.1
  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:9 Changed 9 years ago by yule

The error message is "Could not establish a connection with the server: HTTP proxy connection error 502"

comment:10 Changed 9 years ago by a0z0ra

Anyone got this working?

comment:12 Changed 9 years ago by moo

#186 is duplicate to this one. pls be aware that HTTP GET which is more common, is not the same as HTTP CONNECT.

comment:13 Changed 7 years ago by rekkanoryo

  • Milestone set to 2.6.0
  • Resolution set to fixed
  • Status changed from new to closed

I believe this issue may be at least partially resolved in Pidgin 2.6.0 when it is released. I'm going to mark this as fixed for 2.6.0, but if it's not, I will reopen this ticket.

comment:14 Changed 7 years ago by mipas1

Issue is still not fixed. Please re-open the ticket.

comment:15 Changed 7 years ago by darkrain42

  • Milestone 2.6.0 deleted
  • Resolution fixed deleted
  • Status changed from closed to new

comment:16 Changed 7 years ago by darkrain42

  • Owner changed from marv to sulabh.dev

comment:17 Changed 7 years ago by James

i don't know if it's the same cause, but i also can't conect to yahoo via a proxy. i've attached a log with the error received (but i've censored some irrelevant info)

Changed 7 years ago by James

comment:18 Changed 7 years ago by frqs37

Here are configuration tests that I tried and various results I got:

  • Corp is using proxy server that MUST be set to http://www-proxy.xxx.xx.com:80 and is not allowing SSL tunneling on port 5050
  • If proxy server is set in browser config: browsers can access both http and https web sites
  • If proxy server is set in Yahoo Messenger: we can use YM for chatting

so what configuration in Pidgin did I try and what were the results?

CONFIG 1:

Proxy:  www-proxy.xxx.xxx.com port 80
Pager scsa.msg.yahoo.com port 5050
Use account proxy for SSL connections - checked
Results:  Access Denied: HTTP proxy server forbids port 5050 tunneling

This is the log file:

(21:00:15) dnsquery: Performing DNS lookup for www-proxy.xx.xx.com
(21:00:15) dnsquery: IP resolved for www-proxy.xx.xx.com
(21:00:15) proxy: Attempting connection to 148.xx.xx.xx
(21:00:15) proxy: Connecting to scsa.msg.yahoo.com:5050 via www-proxy.xx.xx.com:80 using HTTP
(21:00:15) proxy: Connection in progress
(21:00:15) proxy: Connected to scsa.msg.yahoo.com:5050.
(21:00:15) proxy: Using CONNECT tunneling for scsa.msg.yahoo.com:5050
(21:00:15) proxy: Proxy server replied with:
HTTP/1.1 403 Forbidden
Content-Length: 1136
Content-Type: text/html; charset=ISO-8859-1
Pragma: no-cache
Proxy-Connection: close
(21:00:15) proxy: Connection attempt failed: Access denied: HTTP proxy server forbids port 5050 tunneling
(21:00:15) connection: Connection error on 02023998 (reason: 0 description: Unable to connect: Access denied: HTTP proxy server forbids port 5050 tunneling)

CONFIG 2:

Proxy:  www-proxy.xxx.xxx.com port 80
Pager scsa.msg.yahoo.com port 80
Use account proxy for SSL connections - checked
Results:  Server closed the connection

This is the log file:

(21:08:50) dnsquery: Performing DNS lookup for www-proxy.xx.xx.com
(21:08:50) dnsquery: IP resolved for www-proxy.xx.xx.com
(21:08:50) proxy: Attempting connection to 148.xx.xx.xx
(21:08:50) proxy: Connecting to scsa.msg.yahoo.com:80 via www-proxy.xx.xx.com:80 using HTTP
(21:08:50) proxy: Connection in progress
(21:08:50) proxy: Connected to scsa.msg.yahoo.com:80.
(21:08:50) proxy: HTTP proxy connection established
(21:08:50) proxy: Connected to scsa.msg.yahoo.com:80.
(21:08:52) util: Writing file prefs.xml to directory C:\Documents and Settings\sberube\Application Data\.purple
(21:08:52) util: Writing file C:\Documents and Settings\sberube\Application Data\.purple\prefs.xml
(21:08:55) util: Writing file accounts.xml to directory C:\Documents and Settings\sberube\Application Data\.purple
(21:08:55) util: Writing file C:\Documents and Settings\sberube\Application Data\.purple\accounts.xml
(21:09:03) yahoo: Error in YMSG stream, got something not a YMSG packet!
(21:09:03) connection: Connection error on 02130688 (reason: 0 description: Server closed the connection)

CONFIG 3: tried taking out "Use account proxy for SSL connections" checkbox No change in results

Considering this issue has been opened 3 years ago, is there a possible ETA? Thank you much

comment:19 Changed 7 years ago by rekkanoryo

In order to successfully take advantage of having the "Use account proxy for SSL connections" option off in this scenario, the global proxy in Pidgin's preferences must be set to "No proxy" and proxies configured on individual accounts.

comment:20 Changed 7 years ago by frqs37

confirmed. this was the setting: global proxy was set to Pidgin pref with No proxy Proxy info was set as previously documented under the Yahoo account Results are previously documented along with extracted debug window info

I realize this is not necessarily an easy issue to fix. On the other hand it is a recognized bug that has taken a long time to be addressed. I think it is reproduceable. As per previous entries:

"Changed 22 months ago by rekkanoryo ¶ status changed from new to closed resolution set to fixed This should be fixed for 2.4.0."

"Changed 7 months ago by rekkanoryo ¶ status changed from new to closed resolution set to fixed milestone set to 2.6.0 I'm going to mark this as fixed for 2.6.0, but if it's not, I will reopen this ticket"

I'm available to test out other settings and beta version if need be.

comment:21 Changed 4 months ago by grim

  • Resolution set to cantfix
  • Status changed from new to closed

The yahoo protocol this ticket refers to has been deprecated by yahoo.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!