[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In 11.10 this configuration is not availaible. Manual config show only server
and port.
No exceptions, no user or password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/284250
Title:
intrepid:
Reported as fixed in Natty. I'd be very tempted to mark this as Fix
Released if others can chime in.
Regardless, proxy is not something done by NetworkManager -- it's either
available at the system level with the HTTP_PROXY/HTTPS_PROXY variables
or via gnome-settings-daemon; so reassigning to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/284250
** Package changed: network-manager (Ubuntu) = gnome-settings-daemon
(Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems to be fixed in natty.
** This bug is no longer a duplicate of bug 556293
sudo does not keep http_proxy environment variable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/284250
Title:
*** This bug is a duplicate of bug 556293 ***
https://bugs.launchpad.net/bugs/556293
This bug is not a duplicate of bug #556293! As was stated above this is
to do with firefox's manner of using the gnome proxy settings. From what
I have seen Google Chrome and Firefox interpret the rules very
*** This bug is a duplicate of bug 556293 ***
https://bugs.launchpad.net/bugs/556293
** This bug is no longer a duplicate of bug 300271
Setting the network proxy doesn't change the synaptic proxy settings
(gnome-network-preferences) for authenticated proxies
** This bug has been marked a
*** This bug is a duplicate of bug 300271 ***
https://bugs.launchpad.net/bugs/300271
Ignoring *.mydomain works fine, bude ignoring 192.* or 192.*.*.* or 192.0.0.0/8
do not work in Lucid Lynx 10.4.
Proxy authentication do not work as described in bug #300271
--
intrepid: network proxy
*** This bug is a duplicate of bug 300271 ***
https://bugs.launchpad.net/bugs/300271
** This bug has been marked a duplicate of bug 300271
Setting the network proxy doesn't change the synaptic proxy settings
(gnome-network-preferences) for authenticated proxies
--
intrepid: network
I have the same bug on my jaunty, 127.0.0.1 does gets proxyied, however
there is the default rule 127.0.0.0/8 on my ignore list. However when I
manually add 127.0.0.1 to that list, firefox uses direct connection.
--
intrepid: network proxy ignore host list ignored for wildcard
This works perfectly for me now at work since upgrading to jaunty.
I put in *.int.company.com and everything on that domain is not proxied.
--
intrepid: network proxy ignore host list ignored for wildcard
https://bugs.launchpad.net/bugs/284250
You received this bug notification because you are
This bug STILL exists in Jaunty. Neither wildcard nor CIDR designation
works in this list.
For enterprise environments this is simply unacceptable.
--
intrepid: network proxy ignore host list ignored for wildcard
https://bugs.launchpad.net/bugs/284250
You received this bug notification because
We have finally convinced the powers that be to let developers use
ubuntu at work - this is a big problem for us as we have a lot of
internal servers, and it would be great to add *.internaldomain.com to
the list instead of each individual server each time...
--
intrepid: network proxy ignore
This can be annoying for users behind company firewalls, where the
company has hosts both inside and outside the firewall that are in the
same domain - eg they're all *.company.com. The only way to distinguish
between intranet and internet hosts is using the subnet - unless you
list every single
I can also confirm this bug with intrepid - it happens to all
applications and not just FF
--
intrepid: network proxy ignore host list ignored for wildcard
https://bugs.launchpad.net/bugs/284250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
i can confirm this bug is still present in intrepid: any wildcard is not
being taken into account in proxy settings
--
intrepid: network proxy ignore host list ignored for wildcard
https://bugs.launchpad.net/bugs/284250
You received this bug notification because you are a member of Ubuntu
Bugs,
Changed package to network-manager since it happens not just to firefox.
I will let n-m triagers decide if correct package.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: firefox = network-manager
--
intrepid: network proxy ignore host list ignored for wildcard
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in:
Yes, it is reproducible..
this is the step:
1. Open System - Network Proxy
2. Set Manual Proxy Config and set your http,ftp,https proxy
3. Now go to Tab Ignored Host, you will see localhost and 127.0.0.0/8 (as
default)
4. Open Firefox and enter on URL: http://127.0.0.1/
this will open proxy's
the issue is not a gnome-control-center one but firefox not using the
GNOME settings
** Changed in: firefox (Ubuntu)
Sourcepackagename: gnome-control-center = firefox
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
Status: Incomplete = New
--
intrepid: network proxy
I don't maybe this is bigger issue... when I try pidgin also happen.. i
tried to add exception to yahoo servers with wildcard... and pidgin
still tries to connect using proxy.. when i add full ip address it don't
use proxy
--
intrepid: network proxy ignore host list ignored for wildcard
22 matches
Mail list logo
