Bug 189835 - don't notify user about a unreachable proxy configuration url so often
Summary: don't notify user about a unreachable proxy configuration url so often
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dawit Alemayehu
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-04-16 21:26 UTC by Marc Schoechlin
Modified: 2018-10-28 03:39 UTC (History)
1 user (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 Marc Schoechlin 2009-04-16 21:26:55 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

If the proxy configuration url is no reachable every few minutes a popup notifies the user about that.
"Could not download the proxy configuration url...."

Firefox never complains about this - firefox simply tries to use a direct connection.

In my opinion it would be the better to notify the user only the first time the url is not reachable.
Comment 1 Dawit Alemayehu 2011-05-17 00:11:48 UTC
This message does not come from kio_http. It comes from the automatic proxy configuration handler which when it fails to download the proxy configuration script warns as mentioned. Re-assigning to kio/general...
Comment 2 Dawit Alemayehu 2011-05-28 00:47:41 UTC
For the record this cannot be compared with how firefox behaves because proxy configuration in KDE is system wide and not specific to one application. As such there is no way for it to know which application it just notified about and which it did not. Also, you get notification only when it attempts to retrieve the proxy configuration file and fail and for any fail it waits a certain period of time before it retries to download the configuration file again. 

Anyhow, will see what can be done about this in the future once all the remaining proxy related issues are ironed out.
Comment 3 Nate Graham 2018-04-25 21:35:33 UTC
Is this still relevant or applicable with KDE Frameworks 5.45?
Comment 4 Andrew Crouthamel 2018-09-28 03:11:46 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 set the bug status 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 5 Andrew Crouthamel 2018-10-28 03:39:32 UTC
Dear Bug Submitter,

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!