#11986: Separate HTTP and IM proxy servers no longer work in 2.7.0
------------------------+---------------------------------------------------
Reporter: psmith2100 | Owner: rekkanoryo
Type: defect | Status: new
Milestone: | Component: unclassified
Version: 2.7.0 | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment(by psmith2100):
When this was working for me in the version before 2.7.0 (2.6.6 I think),
I had an HTTP proxy defined in Preferences / Proxy, and I also had an "IM"
account proxy defined without the "Use account proxy for SSL connections"
box checked.
I have attached a doc file with images of my original proxy settings,
which are the same settings that I have been trying in 2.7.1 and 2.7.2dev
you asked me to try.
The doc file also includes a debug from my last attempt in 2.7.1 as
requested.
Replying to [comment:23 rekkanoryo]:
> Looking at this log, I'm now confused. I want to make sure I'm
understanding your situation correctly here, so I'm going to list what my
current interpretation of your environment is. Please correct me as
appropriate so I can get a complete picture of what's going on here.
>
> Your environment has:
> * One proxy server that handles HTTP and HTTPS, but not any IM
protocols
> * One proxy server that handles IM protocols such as YMSG, but does not
allow HTTP.
> * It's not completely clear to me given the ''whole'' discussion
whether this IM proxy does HTTPS or not.
> * And if the IM proxy does do HTTPS, does Pidgin need to make sure to
send the HTTP request to the HTTP proxy and the HTTPS request to this IM
proxy, or is both HTTP and HTTPS going to the same proxy an acceptable
implementation?
> * Each proxy is a different host with different hostnames/IP addresses
>
> Your original working Pidgin configuration was:
> * Your Yahoo account was configured with essentially all default values
("Use account proxy for SSL connections" turned off being the only default
that's important here)
> * Your HTTP/HTTPS proxy information was configured in the
Tools->Preferences window on the Proxy tab (or pulled in from Internet
Explorer).
> * Your IM proxy was configured on the Yahoo account's Proxy tab.
>
> The reason I'm asking about this is your debug log is indicative of a
different issue that I've not been able to find a root cause for. That
issue, however, is unrelated to our crappy (read: non-existant) handling
of multiple proxy servers, but related to our proxy code being substandard
in other ways. Having a more complete picture of exactly what's going on
here may be helpful in trying to fix both issues.
>
> Additionally, I'm assuming that when you captured the debug log you
posted, you were using the working configuration as described above. If
so, can you please capture another debug log from trying to connect when
using either Pidgin 2.7.0 or 2.7.1 and the described configuration? (I'm
mainly interested in seeing if you get the "authorization required"
response from the proxy server using Pidgin 2.7.0 or 2.7.1 as well.)
--
Ticket URL: <http://developer.pidgin.im/ticket/11986#comment:24>
Pidgin <http://pidgin.im>
Pidgin