Closed Bug 1059141 Opened 7 years ago Closed 7 years ago

Proxy exceptions broken for GUI applications due to missing leading '*' for domain matches

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Attachments

(1 file)

I dislike this endless story about proxies... So at the moment at least on OS X our proxy config is broken for GUI applications. Looks like the changes as went in with bug 997721 were not enough, and the '*' in-front of the domain excludes is really necessary. Not sure when I tested this on OS X when I implemented it for Ubuntu. :/

https://hg.mozilla.org/qa/puppet/file/4bbb537b1d28/manifests/qa-config.pp#l43

.scl3.mozilla.com => *.scl3.mozilla.com

I'm not sure if the no_proxy environment variable on Ubuntu and OS X will support that, so maybe we have to add this in the code of gui.pp. And maybe we should better do the same for Ubuntu too.

Karl, do you have an advice here?
Flags: needinfo?(karlt)
Karl replied to me on IRC. So one solution would be to add duplicated entries just with a leading asterix to the exceptions list. But it's not clear if this can cause side-effects. So better here is really to keep the exception list without asterix, and add them for Ubuntu and OS X GUI proxy settings.
Assignee: relops → hskupin
Status: NEW → ASSIGNED
Flags: needinfo?(karlt)
Summary: QA related proxy configuration broken for OS X GUI applications → Proxy exceptions broken for GUI applications due to missing leading '*' for domain matches
OS: Mac OS X → All
Attached patch gui_proxy v1Splinter Review
Simple substitution to add a '*' in-front of a domain entry with a leading dot.
Attachment #8482420 - Flags: review?(dustin)
Attachment #8482420 - Flags: review?(dustin) → review+
https://hg.mozilla.org/qa/puppet/rev/4a9202786ff0

Crossing fingers that this was the last patch for proxies. Now we should have it.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.