Bug 293082 - proxy exceptions settings does not apply
Summary: proxy exceptions settings does not apply
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_proxy (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-01 20:50 UTC by MohamadReza Mirdamadi
Modified: 2023-02-09 03:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MohamadReza Mirdamadi 2012-02-01 20:50:19 UTC
Version:           1.0 (using KDE 4.8.0) 
OS:                Linux

I use Kubuntu 11.10, KDE 4.8

When I enter addresses in the exception text field, it doesn't work. I mean The proxy applies to all the network.

Even when I check the box for revers exception, it does not work like before.

I used to have this issue since I upgrated to 4.7.4 and now on 4.8.

Reproducible: Always

Steps to Reproduce:
1- go to system settings > Network > Proxy
2- set proxy to manual and configure it
3- enter some addresses in "Exception" field and hit apply
4- open a browser like rekong or a program like choqok
5- The proxy exception list does not work

Actual Results:  
The proxy exception list does not work

Expected Results:  
Proxy Exception list should work properly.

OS: Linux (x86_64) release 3.0.0-15-generic
Compiler: gcc
Comment 1 ro.ggi 2013-02-21 21:06:05 UTC
I noticed that exception-list is used exactly for domains that are included, but if you go with a browser to this domains extern references still goes through a proxy. That is no expected behavior for the browser and it is different in Firefox or Chrome. I think, it should be a specific exception list for this purpose.
Comment 2 Dawit Alemayehu 2013-10-06 13:13:15 UTC
(In reply to comment #1)
> I noticed that exception-list is used exactly for domains that are included,
> but if you go with a browser to this domains extern references still goes
> through a proxy. That is no expected behavior for the browser and it is
> different in Firefox or Chrome. I think, it should be a specific exception
> list for this purpose.

What do you mean? Are you saying if you put an exception for "foobar.com" and visit it, an external reference in that page to say "ads.somehost.com" goes through the proxy? If so, then that is the correct current behavior. I have no idea what Firefox and Chrome do, they exempt all external references from a domain/host listed in the exception box?
Comment 3 Andrew Crouthamel 2018-11-10 03:24:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:38:56 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-10 01:52:26 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-25 05:05:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-09 03:53:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!