desktop-packages team mailing list archive

[Launchpad Bug Tracker <433827@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: curl (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/433827

Title:
  Regression: "Automatic proxy configuration" + gnome-terminal now
  breaks apt-get, curl, wget...

Status in Soup HTTP Library:
  Fix Released
Status in “apt” package in Ubuntu:
  Confirmed
Status in “curl” package in Ubuntu:
  Confirmed
Status in “gnome-terminal” package in Ubuntu:
  Confirmed
Status in “libsoup2.4” package in Ubuntu:
  Triaged
Status in “update-manager-core” package in Ubuntu:
  Confirmed
Status in “wget” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  The fix for bug 48294 -- at least as implemented in gnome-terminal
  2.27.92-0ubuntu1 from Karmic -- may be theoretically more correct, but
  it seems to have broken strictly more apps than it fixes.

  Steps to reproduce:
  1) Go to System -> Preferences -> Network Proxy, select "Automatic proxy configuration", and enter the URL of a PAC proxy (I use http://webproxy.ucsd.edu/proxy.pl).
  2) Start a gnome-terminal.
  3) echo $http_proxy

  Before bug 48294 was fixed, this produced "http://:8080";, which breaks
  wget, but most apps are happy to ignore it this obviously invalid URL.
  One can reproduce the old behavior easily at the command line:

  $ http_proxy=http://:8080 wget google.com # FAILS: "Error parsing proxy URL"
  $ http_proxy=http://:8080 curl google.com # SUCCEEDS
  $ http_proxy=http://:8080 sudo apt-get update  # SUCCEEDS

  With current gnome-terminal, the above steps result in http_proxy
  being set to "pac+http://webproxy.ucsd.edu/proxy.pl";. I cannot find
  any reference to this "pac+http" URL scheme anywhere, and indeed, apps
  do not know how to handle it:

  $ http_proxy=pac+http://webproxy.ucsd.edu/proxy.pl wget google.com # FAILS: "Error parsing proxy URL"
  $ http_proxy=pac+http://webproxy.ucsd.edu/proxy.pl curl google.com # FAILS: "couldn't connect"
  $ http_proxy=pac+http://webproxy.ucsd.edu/proxy.pl sudo apt-get update # FAILS: 404 errors

  So not only did this "fix" fail to fix the old broken software, it
  breaks new software, and the newly broken software is failing in very
  confusing ways.

  In the long run this should perhaps be considered a bug in wget, curl,
  apt-get, and every other HTTP implementation in in Ubuntu, but I'm
  filing against gnome-terminal because 1) that's what caused the
  regression, 2) at this point in the release cycle I'm guessing you
  might want to just unset http_proxy in these proxy auto-config cases
  (none of this software could parse the PAC file anyway, it requires a
  javascript interpreter), rather than try to fix everything
  everywhere...

To manage notifications about this bug go to:
https://bugs.launchpad.net/libsoup/+bug/433827/+subscriptions