Opened 11 years ago

Closed 10 years ago

#6391 closed defect

New-version notification check doesn't work through authenticated proxy

Reported by: ferdez Owned by:
Milestone: Component: plugins
Version: 2.4.3 Keywords: version notification, proxy
Cc:

Description

Although pidgin works well with our squid proxy that requires authentication, the check-for-new-version routine does not work well. And even though it doesn't get through the proxy, it still says every time that a new version is available.

Change History (5)

comment:1 follow-up: Changed 11 years ago by datallah

  • pending changed from 0 to 1

What does the debug log say when this happens?

comment:2 in reply to: ↑ 1 Changed 11 years ago by ferdez

  • pending changed from 1 to 0

Replying to datallah:

What does the debug log say when this happens?

The debug log has the following messages:

=================================================
(07:39:19) util: requested to fetch (http://pidgin.im/version.php?version=2.4.3&build=purple-win32), full=1, user_agent=((null)), http11=0
(07:39:19) dnsquery: Performing DNS lookup for proxy.md.pt
(07:39:19) prefs: /plugins/gtk/relnot/last_check changed, scheduling save.
(07:39:19) connection: Activating keepalive.
(07:39:19) jabber: Sending (ssl): <iq type='get' id='purple2e033658' to='gmail.com'><query xmlns='http://jabber.org/protocol/disco#items'/></iq>
(07:39:19) jabber: Sending (ssl): <iq type='get' id='purple2e033659' to='gmail.com'><query xmlns='http://jabber.org/protocol/disco#info'/></iq>
(07:39:19) dnsquery: IP resolved for proxy.md.pt
(07:39:19) proxy: Attempting connection to 195.23.113.19
(07:39:19) proxy: Connecting to pidgin.im:80 via proxy.md.pt:81 using HTTP
(07:39:19) proxy: Connection in progress
(07:39:19) proxy: Connected to pidgin.im:80.
(07:39:19) proxy: HTTP proxy connection established
(07:39:19) util: Request: 'GET http://pidgin.im/version.php?version=2.4.3&build=purple-win32 HTTP/1.0

Connection: close

Accept: */*

Host: pidgin.im



'
(07:39:19) util: Response headers: 'HTTP/1.0 407 Proxy Authentication Required

Server: squid/2.6.STABLE5

Date: Thu, 24 Jul 2008 06:39:21 GMT

Content-Type: text/html

Content-Length: 1333

Expires: Thu, 24 Jul 2008 06:39:21 GMT

X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0

Proxy-Authenticate: Basic realm="MoreData Squid Proxy"

X-Cache: MISS from sprint.moredata.pt

X-Cache-Lookup: NONE from sprint.moredata.pt:81

Via: 1.0 sprint.moredata.pt:81 (squid/2.6.STABLE5)

Proxy-Connection: close



'
(07:39:19) util: parsed 1333
=====================================================================

This seems to mean that the proxy authentication is not well done in this case. For all other use (like IM itself) the proxy authentication mechanism works well.

comment:3 Changed 10 years ago by bernmeister

Are you getting notifications now using more recent versions of Pidgin?

comment:4 Changed 10 years ago by darkrain42

  • Status changed from new to pending

comment:5 Changed 10 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

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!