[Pidgin] #6391: New-version notification check doesn't work through authenticated proxy

Pidgin trac at pidgin.im
Thu Jul 24 06:18:55 EDT 2008


#6391: New-version notification check doesn't work through authenticated proxy
----------------------+-----------------------------------------------------
  Reporter:  ferdez   |       Owner:                             
      Type:  defect   |      Status:  new                        
  Priority:  minor    |   Milestone:                             
 Component:  plugins  |     Version:  2.4.3                      
Resolution:           |    Keywords:  version notification, proxy
   Pending:  1        |  
----------------------+-----------------------------------------------------
Changes (by ferdez):

  * pending:  1 => 0

Comment:

 Replying to [comment:1 datallah]:
 > What does the [wiki:TipsForBugReports 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.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/6391#comment:2>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list