跳至主要内容

How to Configure Network Proxy Settings for OSX

 原文链接

Once the domain of Windows clients, more MacBooks and iMacs are finding their way onto small business and corporate networks. These networks typically funnel all Internet-bound traffic through a number of proxy servers.

Any application that requires Internet access will need point traffic towards them. Of course, the network itself usually will not tell you to do so, so we’ll need to tell our Mac to use them.

Proxies can be configured a number of ways, depending on your needs. Desktop applications use the network settings found under System Preferences. However, anything executed from a terminal window may require alternative settings.

Terminal

Developers, DevOps, and administrators spend a lot of their time in Terminal. Unfortunately, the proxy settings set in System Preferences won’t apply here. Instead, we’ll need to set a few environment variables: http_proxyhttps_proxy, and no_proxy.

Environment Variables

When to use: quick and dirty ephemeral network configuration settings. These settings only affect the Terminal window session they are used in, and exist for only as long as the session is open.

  • Execute one or both of the export commands for HTTP traffic. Most applications will work with the lowercase version, but there are edge cases that require uppercase.
    export http_proxy=192.168.1.10:8080
    export HTTP_PROXY=192.168.1.10:8080
  • Same as with HTTP, use one or both the examples below for HTTPS traffic.
    export https_proxy=192.168.1.10:8080
    export HTTPS_PROXY=192.168.1.10:8080
  • Not all traffic should funnel through your network’s proxy. Typically, all local network traffic should go directly to its destination. We can enforce this by using the no_proxy environment variable.
    export no_proxy=localhost,127.0.0.1,*.my.company.lan

User Profile

When to use: When you need persistent proxy configurations between Terminal windows.

  1. Open ~/.bash_profile into a text editor
  2. Add the following contents to the file, replacing my.http.proxy.server:8000 and my.https.proxy.server:8000 with the URL and port of your proxy server.
    httpProxyServer=my.http.proxy.server:8000
    httpsProxyServer=my.https.proxy.server:8000
    
    export http_proxy=$httpProxyServer
    export https_proxy=$httpsProxyServer
    export HTTP_PROXY=$httpProxyServer
    export HTTPS_PROXY=$httpsProxyServer
  3. Save your changes.
  4. Open a new Terminal

Every new Terminal window should now have your proxy settings configured.

Network Configuration

In order for your desktop applications, such as Safari and Chrome, for example, you will need to tell them where to forward Internet traffic to. This can be done in the Network configuration screen, under System Preferences.

  • From Launchpad., open System Preferences
  • Select Network.
  • Click the Proxies tab.
  • Under the ‘Select a protocol to configure‘ list, check the protocol you want to set the proxy for. In the example below, we’re providing settings for HTTP and HTTPS traffic.
  • Enter the hostname or IP address of the proxy server in the Web Proxy Server form field. The field next to it is where you set the proxy’s port number.  If you require a username and password, enter them into the appropriate fields

    Network Proxy Settings for HTTP
    Network Proxy Settings for HTTP
  • Click OK to save your settings.

评论

此博客中的热门博文

Resolving errSecInternalComponent errors during code signing

原文链接 One code signing issue I commonly see, both here on DevForums and in my Day Job™ with DTS, is that the codesign command fails with errSecInternalComponent. This issue crops up in a wide variety of circumstances and the correct fix depends on the specific problem. This post is my attempt to clarify the potential causes of this error and help folks resolve it. If you have any questions or comments about this, please start a new thread, tagging it with Code Signing so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Resolving errSecInternalComponent errors during code signing In some circumstances the codesign command might fail with the error errSecInternalComponent. For example: % codesign -s "Apple Development" "MyTrue" MyTrue: errSecInternalComponent This typically affects folks who are signing code in a nonstandard environm...

iOS:检测使用VPN或Proxy

参考链接: https://www.jianshu.com/p/c3b950dbf86a https://gist.github.com/PramodJoshi/4faad4c91f7dcb4eb9b06be8390c01db http://noodlecode.net/2018/04/check-if-ios-app-is-connected-to-vpn 第一种方法 需要导入框架CFNetwork 然后,这个方法是mrc的:需要添加-fno-objc-arc的flag 代码如下: + ( BOOL )getProxyStatus { NSDictionary *proxySettings = NSMakeCollectable ([( NSDictionary *) CFNetworkCopySystemProxySettings () autorelease]); NSArray *proxies = NSMakeCollectable ([( NSArray *) CFNetworkCopyProxiesForURL (( CFURLRef )[ NSURL URLWithString: @"http://www.google.com" ], ( CFDictionaryRef )proxySettings) autorelease]); NSDictionary *settings = [proxies objectAtIndex: 0 ]; NSLog ( @"host=%@" , [settings objectForKey:( NSString *)kCFProxyHostNameKey]); NSLog ( @"port=%@" , [settings objectForKey:( NSString *)kCFProxyPortNumberKey]); NSLog ( @"type=%@" , [settings objectForKey:( NSString *)kCFProxyTypeKey]); if ([[settings object...

去广告DNS设置,国内ADGuard DNS方案,手机电脑iOS去广告,保护隐私

 原文链接 之前分享过使用mac系统搭建adguard home,这几个月用下来零零散散基本上也被弃用了。主要原因是因为需要保持电脑一直开机。但是我的电脑是笔记本,存在移动各个地域的情况,也就是说只能够屏蔽电脑自身,对于手机而言不太现实。今天偶然发现dnspod推出了高级版的公共解析。dnspod背靠腾讯云,肯定是合法合规的公共解析服务,这个高级版用起来不错。 国内自己搭建解析服务是违法行为,所以这也是为什么使用dnspod的原因。 后台截图 开始使用 首先我们先进入dnspod的公共解析页面,点击开始使用。 专业版公共解析 dnspod会提供几种预设,我们选择「开发者」即可 开发者 然后你就成功的申请到自己个人使用的dns了! 更新拦截规则 我们可以将常见的广告过滤规则加入到dns中。我们在顶部选项卡中选择「拦截规则」。 拦截规则设置 打开adguard adguard 绑定iOS设备 推荐使用描述文件的方式,删除配置时删除描述文件即可。 描述文件 绑定macOS 推荐使用描述文件的方式,删除配置时删除描述文件即可。 描述文件 mac需要在「系统偏好设置」的「网络」中查看是否正在运行。 代理 如果没有运行需要点击「···」来启动服务。 启动服务 绑定路由器 找到自己路由器的DHCP设置,修改dns,然后记得绑定自己的ip。 修改dns 绑定ip 费用 目前有300万次/月的免费额度,但没有超出之后的价格。300万次一个人比较难用完,可以放心使用。 我个人使用iOS设备两台、智能家居、电脑两台,日均请求数大致2万/日。 判断是否搭建成功 可以通过查看日志的方式,日志大概有半小时到一小时的延迟,请耐心等待。