User Profile

We use a proxy.pac file to redirect connections to blacklisted URLs by PROXY-ing the request to a local server proxy. For example, the proxy.pac file sends requests to https://unwarranted.tracker.website/?whatever to PROXY http://my.blackhole.server:8119 This has worked for years on Safari iOS, and still works on Safari macOS, but has stopped working for HTTPS requests on all i-devices after updating to Safari on iOS/iPadOS 15. Most requests are HTTPS. The observed behavior is that Safari 15 bypasses the PROXY and sends requests to https://unwarranted.tracker.website/?whatever. I hypothesize the reason is that the proxy returns 400 for such HTTPS CONNECT requests. Its behavior, expected for HTTPS CONNECT requests,looks like: curl -I --proxy http://my.blackhole.server:8119 https://unwarranted.tracker.website/?whatever. HTTP/1.1 400 Bad Request Server: nginx/1.21.3 Date: Sat, 25 Sep 2021 19:17:07 GMT Content-Type: text/html Content-Length: 157 Connection: close curl: (56) Received HTTP code 400 from proxy after CONNECT Is bypassing a proxy.pac’s PROXY if the proxy server returns a 400 code expected behavior for Safari iOS? We would like to be able to block unwanted requests on iOS with a proxy.pac file.

I use the "launchctl setenv" command to set shell environment variables used by launchd launch daemons.The man pages "man launchctl" say that "launchctl export" will show all variables used by launchd:export Export all of the environment variables of launchd for use in a shell eval statement.But "sudo launchctl export" throws an error":Unrecognized subcommand: exportWhat commnd shows all shell environment variables set and used by launchd launch daemonds?This is on macOS 10.14.6.