10952 2017-01-23 03:31:00 +0000 no_proxy handling has changed 2017-07-17 17:15:55 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED Medium normal 2.3 1 denis joshuagloe patrick.ohly poky.bs.watcher poky.watcher --- --- Yes (doc changes required) oldest_to_newest 69995 0 denis 2017-01-23 03:31:00 +0000 According to the following Wiki page, no_proxy variable takes list of domains in the form of ".example.com" - i.e. with a leading dot: https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy It actually used to work fine like that for quite some time (past few years) - we've been using SSTATE_MIRRORS inside a local network behind a proxy, that had its domain listed in no_proxy variable with a leading dot. Something has changed recently and the only change I can think of is that build machines were upgraded from Ubuntu 16.04 to 16.04.1 - SSTATE_MIRRORS stopped working. Debugging showed that it would fail to resolve the URL, even though running manual wget command with the same URL would work. Then I stumbled upon the original World Wide Web Consortium page about proxy variables and noticed that no_proxy actually takes a list of domains WITHOUT leading dots: https://www.w3.org/Daemon/User/Proxies/ProxyClients.html Sure enough, making the change to no_proxy variable to list "example.com" w/o a dot fixed SSTATE_MIRRORS! I'm guessing some Python library in Ubuntu 16.04.1 got updated and it's now more strict to how it parses no_proxy variable, but I haven't looked that far yet, sorry. 70468 1 joshuagloe 2017-02-07 13:14:28 +0000 Thanks for the report Denys. Sounds like we should just update the wiki page to use the correct syntax as defined by the W3C? If you don't have a wiki account I can take care of that for you? 70784 2 denis 2017-02-17 00:44:28 +0000 Joshua, I'd like someone to first verify and confirm my finding before actually changing the documentation. Thanks. 70809 3 joshuagloe 2017-02-17 14:34:59 +0000 Denys, it took me a while to set up an environment to test but I can confirm that with a no_proxy variable with domains of the form ".example.com" bitbake fails to fetch from my shared state mirror on my corporate network, with a no_proxy variable with domains of the form "example.com" objects are fetched and used from the shared state mirror. Testing was performed with a Fedora 25 build machine 71004 4 denis 2017-03-01 03:35:58 +0000 Thanks for the confirmation! Should documentation now be updated accordingly? 71016 5 joshuagloe 2017-03-01 11:04:03 +0000 (In reply to comment #4) > Thanks for the confirmation! Should documentation now be updated accordingly? I inferred that you were going to edit the wiki, could you? 71049 6 joshuagloe 2017-03-02 16:50:30 +0000 Wiki page updated. 71051 7 denis 2017-03-02 17:20:18 +0000 Thanks! I wonder if more explicit statement about not using leading dot is needed on the page itself, similar to what is said in change log... 75075 8 patrick.ohly 2017-07-17 17:15:55 +0000 Leading dot will be supported again in some versions of Python - see https://bugs.python.org/issue29142